I'm not an expert, but you you could read somthing about read-opnly flag on jaws.xml

http://www.jboss.org/online-manual/HTML/ch06s03.html

You also could take a look to adavanced container configuration in

http://www.jboss.org/online-manual/HTML/ch07s16.html

try this: if you are accessing many methods of multiple "read-only" entity beans, make sure you set the transaction on these methods to RequiresNew. if you dont then all the calls on your entity beans become part of the same transaction and you will be locked out of all of them while the first transaction completes. if its "read-only" and not changing in the back-end make sure you have commit-option A (or perhaps even D).

c

p.s. there is a transaction type that "suspends" the running transaction call that could be faster than starting and ending a new transaction for each call, but i had problems with it in an earlier jboss version so i havent tried it again since.

Very recently in 3.0 or 3.1 some code was added that, for declared read only entities, locks the instance only for the duration of the method call, not the transaction. This relies on the interceptors not the persistence manager so it must be controlled from jboss.xml, and should work fine for BMP. However I'm not sure if it is in 3.0 RC1 or added just after that. You may have to check the cvs logs for the locking interceptors.

i have tried the same thing but not able to define my entity beans as read only.it is still allowing me to update data

has any one able to implement the read only entity beans properly? i have tried to define the entity beans as commit option D and defined <trans-attribute> as RequriresNew.even than entity is allowing to update its fields.

has any one able to implement the read only entity beans properly? i have tried to define the entity beans as commit option D and defined <trans-attribute> as RequriresNew.even than entity is allowing to update its fields.