More data: AccountEJB.java from the Sun j2ee tutorial grabs a Connection in setEntityContext(), holds onto it until unsetEntityContext(), and uses it for all database work in the mean time. This doesn't seem to agree with the 1.1 spec (page 168) which shows example code grabbing and releasing the Connection in the same method. If I hack the code to grab and release in each method then it seems to work as expected. Guess I'll point this out to Sun. Am I right in thinking that holding on to the Connection is a bad idea and interferes with the container's container-managed demarcation? Thanks, Toby Cabot > I'm getting my feet wet porting some of the Sun j2ee tutorial code > (stateless session "Converter", BMP entity "Account") over to jboss > 2.0 and postgresql 7.0. It's been pretty straightforward so far, > except for one issue: it appears that the Sun BMP code assumes (and > the Sun > reference j2ee container implements) that jdbc connections are by > default AutoCommit true, since the AccountEJB code never calls >setAutoCommit() or commit(), but the results *are* committed to the >database. > > In jboss/postgresql it looks like AutoCommit is false by default > since I get the same behavior if I explicitly setAutoCommit( false) > that I get if I do nothing (i.e. results never committed to db). _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
