-
1. Re: Unable to create read-only/"static" beans...
jcordes Oct 11, 2003 2:45 AM (in response to aparaapara)Give container-configuration "Standard CMP 2.x EntityBean with cache invalidation" a try. BTW: Why not using XDoclet for generating deployment descriptors ?
HTH,
Jochen. -
2. Re: Unable to create read-only/"static" beans...
aparaapara Oct 11, 2003 3:14 PM (in response to aparaapara)Hey, that worked, but why? Also, do I need to say read-only in the jbosscmp-jdbc.xml as well as in the jboss.xml?
I am migrating from a different application server so the code was not written using XDoclet to begin with. I first want to get a hang of JBOSS before jumping into a different development environment.
Thanks.
-AP_ -
3. Re: Unable to create read-only/"static" beans...
aparaapara Oct 11, 2003 3:26 PM (in response to aparaapara)Actually, it did not work. I forgot that last night I put in some optimization code which cached the "static" entity in a static field (not the best thing in the world). Once, I changed the code back, I am seeing findByPrimaryKey executed again.
The only odd thing that I could think of why this is failing to cache is because .jar boundries are being crossed. My "service" beans are in service.jar while my model beans are in "model.jar". But I am not sure if this would make such a difference.
-AP_ -
4. Re: Unable to create read-only/"static" beans...
jcordes Oct 12, 2003 1:46 AM (in response to aparaapara)Did you try to set the commit option to A ? At least that's the configuration for cache invalidation. Also have a look at this great article http://www.onjava.com/lpt/a/3871 for tuning jboss CMP performance.
HTH,
Jochen.