read-only in jboss.xml vs. jaws.xml

[marvil]

In jboss.xml, it is possible to specify an entity bean as read-only, which means "The bean will never be ejbStored" (according to jboss_3_0.dtd). In jaws.xml, it is possible to specify an entity bean as read-only, which means "Do not persist any changes to the bean's state."

So, my simple question is: What is the difference between these two settings? We have tried using read-only in jboss.xml paired with commit-option D, it doesn't seem to work as announced, so perhaps read-only in jboss.xml is the way to go.

[dsundstrom]

I can't tell you about JAWS, but in JBossCMP you get an exception if a readonly cmp-field is changed.

[attachvishal]

can't we make whole entity bean as read only instead of marking fields as read only

[dsundstrom]

Sure. This is one of JBoss's internal problems. In the persistence layer it means that if you change something it is an exception, in the server layer it means 'don't start a transaction and don't lock'. Both support entity level, so you choose which one you want. In Jboss 4.0, we will integrate these ideas. JbossCMP was developed independenly of the container in 3.0 because of the massive changes in CMP 2.0.