On Wed, 24 Apr 2002, Jason Dillon wrote:
> > Tyrex works in 3.0 (at least it did about 2 months ago when I patched it > > up). I would not recommend Tyrex for work in distributed transactions, > > because it would be very slow. It should work fine as a local TM as well > > but, probably, it is slower than JBossTX. To get it to work you would have > > How much slower compaired to how much more robust? Can we fix some of its > slowness? I have no idea how much slower it is. Are there any speed tests in the testsuite? > > I don't have lots of evidence to back this up yet... but I think our fast tx > manager is not very robust and reliable... but that is just a feeling I have > right now. > > I would rather have slower and more stable than super quick... but right now I > would not trust using Tyrex, because hardly anyone uses it with JBoss. Hey, it is just a matter of trying it out. Someone has to start, the rest will follow :) Not that I'm advocating Tyrex here. > > It's open source (are the licenses compatible... don't know, have not cjecked > what the exact license is), if it is more feature rich why don't we integrate > it at the source level then work on fixing its speed issues? > It is a big and complex beast. I remember digging through it when I found some bugs, shrug ... It implements all the CORBA JTA stuff for distributed TXs. I just wrote a hack to propagate the transaction context together with JBoss MethodInvocation, instead of CORBA ORB -- the way Tyrex would do it. Anatoly. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
