XA annoyances

Annoying problem presented itself today. There was a set of updates / inserts that were supposed to being executed as part of an XA transaction. The first part of the updates went properly but when the second half went to execute a JNDI NameNotFound exception was thrown. It turns out that the connection being used in the first part was not actually using an XA driver at the time. This caused the JNDI lookups from the seconds server to be performed against the JNDI tree of the first server. The way this bug presented itself was just really annoying. Argh.