Manik Surtani wrote:
On 27 Mar 2008, at 20:17, Brian Stansberry wrote:
> Manik Surtani wrote:
>> What do you guys think? Too many people try and use this in
>> production and then complain that it doesn't work. It is not
>> transactional and cannot withstand a JVM crash midway during a write.
>> Should we deprecate this in 2.2.0 and remove it in 3.0.0?
>> I know that JBoss AS uses it in some cases, but can that not be
>> changed to use the JDBM cache loader?
>
> No, it can't. :( Unfortunately, JDBM appears to be a pretty dead project.
"Mature", as some may call it. :-) I was just having a conversation
with the JDBM lead the other day - it's certainly not abandoned or
anything.
Well, that's good. The last release was 1.0 in Aug 2005.
Passivating sessions is a pretty important use case. With FCL, warts
and all, I know where the pain points are (and they aren't as bad, since
passivation isn't transactional).
> FCL is just an impl of a pluggable interface though. If you
don't want
> it in 3.0 and if we can't find a valid replacement by the time AS is
> ready to consume 3.0, then I can always pull the FCL code into the
> AS/EJB3 source tree.
That is always an option, I guess. Shall we stick with deprecating it
in 2.2 and removing it in 3.0 then?
OK by me. Posting on the user forum about it is probably not a bad idea
though.
Cheers
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com