Commit option B doesn't give you anything anyways in JBoss unless you are doing non-transactional requests on your entity beans. Since this is a rarity, I didn't put much thought into commit-b optimizations for the multiinstance interceptors.
Bill > -----Original Message----- > From: Henri Chen [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 09, 2002 9:46 AM > To: [EMAIL PROTECTED] > Cc: Bill Burke > Subject: RE: [JBoss-dev] RE: Bug in > EntityMultiInstanceSynchronizationInterceptor.java ? > > > Is this implies that there is no Option B in jboss 2.4.4 at all > because option B virtually equals to option C? > > Henri > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Bill > Burke > Sent: Tuesday, April 09, 2002 9:09 PM > To: Henri Chen; [EMAIL PROTECTED] > Subject: [JBoss-dev] RE: Bug in > EntityMultiInstanceSynchronizationInterceptor.java ? > > > This is because we trash the instance. > > > -----Original Message----- > > From: Henri Chen [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, April 09, 2002 4:40 AM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: Bug in EntityMultiInstanceSynchronizationInterceptor.java ? > > > > > > Dear Bill, > > > > Sorry to bother you again. This is based on the jboss 2.4.4 source code. > > > > According to the ejb 2.0 spec as seen on P.210, in Option B, the > > instance should only be marked as "invalid state" inside > > afterCompletion(). However, the > > EntityMultiInstanceSynchronizationInterceptor.java > > implementation of jboss 2.4.4 always calling ejbPassivate() no > > matter it is Option B or Option C. > > > > Henri Chen > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
