4 Replies Latest reply on Oct 12, 2003 1:46 AM by jcordes

Unable to create read-only/"static" beans...

aparaapara Oct 11, 2003 2:30 AM

I am trying to configure (JBOSS3.2.2RC3)a few beans for read-only type of access, but I am still seeing findByPrimaryKey being executed.

In jboss.xml:

<ejb-name>ComponentType</ejb-name>
<read-only>true</read-only>
<configuration-name>Standard CMP 2.x EntityBean (static final entity)</configuration-name>

...

<container-configuration extends="Standard CMP 2.x EntityBean">
<container-name>Standard CMP 2.x EntityBean (static final entity)</container-name>
<call-logging>false</call-logging>
<sync-on-commit-only>false</sync-on-commit-only>
<insert-after-ejb-post-create>false</insert-after-ejb-post-create>
<commit-option>D</commit-option>
</container-configuration>

In jbosscmp-jdbc.xml (I am not sure why I have to specify read-only in both places):

<ejb-name>ComponentType</ejb-name>
<read-only>true</read-only>
<table-name>componenttype</table-name>

However, I am still seeing:

02:01:00,870 DEBUG [findByPrimaryKey] Executing SQL: SELECT id, name, description, componentValueHomeName FROM componenttype WHERE id=?

Am I missing something else?

Thanks.
-AP_

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.
Actions
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_
Actions
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_
Actions
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.
Actions

Go to original post