Hi Luke,
> Would it be true to say that JBoss implements option A? I am
> certainly seeing this type of behaviour with my session wrapped
> entity beans, i.e. no ejbLoad() called for new Transactions after
> the initial find/ejbActivate combo. ...
Yes, the default configuration for JBoss is commit option A.
> ... Is it possible to configure JBoss to use one of the other
> options mentioned in the spec? I.e. I basically need ejbLoad to
> be called on the entity beans afresh in each transaction.
Yes, have a look into the docs at
http://www.jboss.org/documentation/HTML/ch06s08.html
and search for <commit-option>. JBoss supports all options from
the spec (A, B and C) plus another JBoss special one.
There are rumors, that option C does not work correctly (it's
told, that the entity bean is not reloaded at start of a new
transaction). I can't believe that, but I havn't tested that
myself. If you plan to use commit option C you must be sure to
declare your methods as transaction required INCLUDING the
finders!
But just in case I repeat what others did to ensure reloading:
they have set <min-capacity> and <max-capacity> in the
<cache-policy-conf> to exactly 1 (same document as above).
regards
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
