This transactional behavior can be modified. Please see
http://www.jboss.org/documentation/HTML/ch06s08.html for more details.
---
Michael R. Maraya
> ----------
> From: Luke Studley[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Wednesday, July 18, 2001 6:29 PM
> To: '[EMAIL PROTECTED]'
> Subject: [JBoss-user] JBoss Entity Bean Transactions
>
> Hi all
>
> In the ejb 1.1 Spec (pdf) 9.5.4 and 9.5.5 (ending and starting new
> transactions for entity beans) it mentions 3 options for a container to
> end a transaction:
> A. mark "not registered"
> B. mark "invalid state"
> C. ejbPassivate()
>
> Which relates to the following actions for starting the next transaction:
> A. Do nothing
> B. ejbLoad()
> C. ejbLoad()
>
> 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.
>
> If this is the case then you cannot pick up new transaction data changed
> in the dB from outside of JBoss without restarting or re-deploying your
> beans. Which is quite annoying for the application I have.
>
> Is any / all / none of this true?
> 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.
>
> As always any answers appreciated.
>
> Thanks
>
> Luke
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
