I think JBoss calling ejbStore before the call the BMP2 methodC is not a bug, but that not calling it again at the end of methodB is a bug. I'd expect you'd only notice this with commit option B or C or looking directly at the db?
The only place that currently knows what the call stack of ejbs is is the CachedConnectionManager, notified by the CachedConnectionInterceptor. This could be modified to check on the return from an ejb call whether the caller was an entity bean, and add it to the global tx entity map if it is. Thanks david jencks On 2002.06.04 06:53:57 -0400 [EMAIL PROTECTED] wrote: > > > Hi Everybody, > I'm using JBoss3.0.0 with tomcat 4.0.3 and SQL Server 2000. > I have a strange problem in this scenario: > Session Bean methodA()-->BMP1 methodB()-->BMP2 methodC(). > I found that ejbStore() of BMP1 was called in middle of methodB() just > before I > lookup and call BMP2,so the rest code of methodB() was not persistent to > DB.I > have deployed the same code on J2EE RI and Weblogic 6.1, and both runs > well.Is > this a JBoss bug or am I wrong somewhere? > Thanks for your help! > Max > > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
