Subject | Non-JCA XA capability? |
---|---|
Author | rboerdijk |
Post date | 2003-03-08T11:09:45Z |
Hi,
I would like to use the XA capabilities of the Firebird JDBC driver
in a non-JCA environment. From the FAQ I read that this is not
possible but I wonder why. Most other XA-compliant JDBC drivers I
have looked at do not have this limitation and from the JTA spec, I
also don't see any strict reason for this linkage. Are there any
technical reasons for linking the XA capabilities to JCA? Would it be
possible to remove this linkage so that the it can also be used in a
non-JCA environment?
Thanks,
Robin Boerdijk
I would like to use the XA capabilities of the Firebird JDBC driver
in a non-JCA environment. From the FAQ I read that this is not
possible but I wonder why. Most other XA-compliant JDBC drivers I
have looked at do not have this limitation and from the JTA spec, I
also don't see any strict reason for this linkage. Are there any
technical reasons for linking the XA capabilities to JCA? Would it be
possible to remove this linkage so that the it can also be used in a
non-JCA environment?
Thanks,
Robin Boerdijk