I guess I don't understand. Does this other OR-mapping system do
a manual commit or rollback on the connection? If so, you don't need to
use the Minerva wrappers at all - you can set up a plaing JDBC pool where
there's no interaction with the TM and it's up to you to manually commit
or rollback.
Or are you saying that a commit action would proceed through the
TM but a rollback would not?
Aaron
On Thu, 2 Aug 2001, Jung , Dr. Christoph wrote:
> 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
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
