Most other xa jdbc drivers were written before the jca spec existed, so
since they are based on the xa jdbc spec they do not have the more advanced
features of a jca adapter. IMO the jca design is a very significant
improvement over the xa jdbc design. Writing wrappers for XADatasource
and XAConnection around ManagedConnectionFactory and ManagedConnection
should not be too hard if you are really interested, since it mostly
involves concealing functionality.

I'm rather curious as to what environment you have that has an xa
transaction manager but does not support jca adapters.

david jencks

On 2003.03.08 06:09 rboerdijk wrote:
> 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
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>