-----Ursprüngliche Nachricht-----
>Von: Aaron Mulder [mailto:[EMAIL PROTECTED]]
>Gesendet: Mittwoch, 1. August 2001 17:37
>An: Jboss-Development (E-Mail)
>Betreff: Re: [JBoss-dev] jbosspool (another one for the XPs) :
>implementation of org.jboss .pool.jdbc.xa.wrapper.XAClientConnection
>I preferred to not allow a manual rollback at all. It is probably
>the case that the exception will ultimately cause a rollback. However, if
>the exception is supressed for some reason, we wouldn't want the bad code
>that called rollback on the connection to cause data integrity problem
>with good code operating on the same connection in the same transaction.
Maybe I should have stated that we use a *non-xa* jdbc connection
underneath.
The minerva wrappers are then dispensed, inter alia, to another level of
pooled,
transactional OR-mapping resources. In this context, the
XAClientConnections are used without immediate tx
association and are purely controlled by the managed OR-resources. Hence the
automatic rollback
on the OR-Resource will force a "manual" rollback of the ClientConnection.
Hence, I´m not trying to convince you to remove that Exception if the
XAClientConnection wraps an
xa jdbc connection! Here, the code is perfect. I´m rather asking for an
analogue implementation to
the commit case, where you also throw an Exception in the xa-case but do the
manual commit, otherwise.
Thx for your attention,
CGJ
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
