Hello,
Does the MarshalledValue solution implie that my POJO will be serialized on put and
deserialized on get. If that is true, it would seriously degrade the perfomance as I
cache quite large objects.
Norbert: As a workaround you may include the classes in the servers classpath, so the
Does the MarshalledValue solution implie that my POJO will be serialized on put and
deserialized on get. If that is true, it would seriously degrade the perfomance as
I cache quite large objects.
correct. That's why storing references to the actuall object itself is choosen for the
local
I have also put a faq on class loading scope regarding to JBossCache (and caching
system, in general, AFAIK). Here is the url:
http://docs.jboss.org/jbcache/FAQ.html
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3847016#3847016
Reply to the post :
this is due to the fact that objects in the cache that is residing in the same JVM as
the ejb are accessed by reference without any check whether the previous loaded
classes of these objects are accessible to the current ejb's classloader anymore. This
isn't easy to solve as long the objects
This classloading issue is also disucssed here:
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842379
There is really no good (optimized) solution to it except to have another in-vm cache
per ejb app.
I have also put it under the latest FAQ. Check it out.
-Ben
View the original post
