Hi!
Rickard �berg wrote:
> Hi!
>
> Tommy Hellstr�m wrote:
> >
> > Marc and Richard,
> >
> > I have to agree that some time has passed since I was reading the relevant
> > specs, but...
> >
> > JTS. Isn't JTS required in a J2EE implementation?
>
> Nope.
> > Isn't JTS required to be able
> > to communicate with other's TM's?
>
> Only if they are from another vendor and that other vendor uses JTS.
Exactly. But I expect other vendors to support JTS so isn't it a good thing to
support it in jBoss as well?
>
> > I wouldn't say that writing a completly new TM is "no biggie" when it comes to
> > distributed 2PC with failure handling and so on.
>
> Most of the tricky stuff is handled by the XAResources. Creating a TM is
> mostly about pushing the right buttons at the proper times. Takes some
> thinking but isn't exactly rocket science. The specs are very clear and
> have good examples.
The spec is pretty good along with an understanding of OTS. I do not think it is
rocket science either but I really think that it is quite complicated when it comes
to supporting transactions that spans more than one TM or even with more than one
XAResource (RM). Cause a RM can't help you much for distributed transactions. What I
think makes it hard is the OTS concept of "subordinate coordinates" (I think all TM
implementations need that, no matter if it is an OTS implementation or another.) and
the large amount of possible failures that can happen, still, it isn't rocket
science but I still think it is a programming task that required a lots of time to
be stable and complete.
Regards,
/Tommy
