Hi,
all work you do on transactional resources will be rolled back. If you
find a way to access a non-transactional resource (some versions of mysql,
I think message queues if you don't use jmsra, non transactional features
of an rdbms such as generators/sequences) those actions will not be rolled
back.
If you have an error during the commit process and are accessing more than
one resource you need true xa-capable drivers for every resource for proper
rollback to occur; the standard "XADataSourceImpl" wrappers for jdbc 1
drivers not xa-capable and may leave your resources in inconsistent states.
david jencks
On 2001.08.05 23:59:28 -0400 Ivan Novick wrote:
> Hi,
>
> If a bean is labeled container transaction in the deployment desrciptor,
> does that mean that if I execute 100 lines of code in a session bean
> method,
> they will all be reversed if an exception occurs, including all writes to
> a
> database using JDBC?
>
> My guess is probably no, but then what is the point of container managed
> transactions?
>
> Regards,
> Ivan
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
