Why do we have to work around driver bugs at the transaction manager
level? Why not write the TM the way we want and start introducing driver
specific JCA wrappers to deal with these issues?

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message ----- 
From: "Ole Husgaard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 08, 2002 10:53 AM
Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on closed XAResources


> Larry Sandereson wrote:
> > +1 for changing JBoss TM to allow end(success) on suspended tx without first
> > calling start(resume).
> 
> Seing that this would give problems with the drivers of two
> major databases made me change my "vote" on this from +1 to
> +0.
> Really, should we drop support for Oracle and Sybase?
> 
> Still, doing the change would IMHO be the right thing
> to do from a purely technical viewpoint (they should fix
> their bugs!).
> 
> > I would still like to pursue closing resources with TMSUCCESS, though.  If
> > nothing else, it removes the need to call 'end' twice.  More importantly, it
> > seems to me like that is the intent of the JTA spec.  I will find some time
> > this weekend to investigate SwiftMQ and JBoss TM.
> 
> That would be fine. If this can be done, doing the other
> change would not be as urgent, and we could wait until the
> database vendors have fixed their bugs.
> 
> Best Regards,
> 
> Ole Husgaard.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to