Basically, no. 2.4 behavior is wrong, 3.x behavior is according to jca spec.
In either case you should be able to do: Connection con = ds.getConnection(); con.setAutocommit(false); //do work con.commit(); I don't know if it would work in 2.4 but you could also use UserTransaction in 3.x david jencks On 2003.02.13 18:07 "Sonnek, Ryan" wrote: > migrating a small jsp app that uses an oracle database from jboss 2.4.6 > to > 3.0.6, the following error is recieved from a page that calls commit() > after > an insert/update/delete. > > "You cannot commit with autocommit set!" > > in 2.4, the commit was required to get any of our pages to work, and now > they fail with this error. is there some way to configure a datasource > in > 3.x to have autocommit set to false, or in 2.4 to set it to true? > > thanks ahead of time. > Ryan > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
