So while I'm on the topic, I read through the JTS spec. From
that, it looks like you must run an ORB within your app server to support
JTS (no surprise, since it uses IIOP). Ordinarily, this shouldn't be a
problem, since the JDK includes an ORB.
However, there's that bit about startup, where the ORB and
TransactionService are supposed to perform a variety of lookups and
callbacks to identify each other. It seems like this is pretty
non-standard. How would the JDK ORB be able to lookup the correct part of
an arbitrary JTS implementation (in JNDI, I think)? Does this imply that
each container needs to include a custom ORB in order to support JTS?
That would be pretty unfortunate.
This whole OTS/JTS business is about as clear as mud to me. Is
there anyone out there who has a better understanding? Or at least,
anyone who has actually used this in practice to link up disparate
transaction management systems? I can't even think of an example where
OTS interoperability would be necessary, which probably just goes to show
how poorly I understand it.
Thanks,
Aaron
