Standalone Narayana: spurious dependency?

[ljnelson]

Hello; I continue to play around with Narayana in a CDI 2.0 SE environment (i.e. no app server, no JNDI, etc.).

I noticed that the narayana-jta artifact brings in a JCA dependency.  Here's part of the output from mvn dependency:tree:

\- org.jboss.narayana.jta:narayana-jta:jar:5.9.0.Final:compile

   +- org.jboss:jboss-transaction-spi:jar:7.6.0.Final:compile

   \- org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec:jar:1.0.0.Final:compile

JTA in general doesn't require these classes, right?  Is this compile-time (and therefore also runtime) dependency intentional?

Anyway, just wanted to get a sense of what would go boom if I exclude this.  Nothing seems to break for normal JTA use cases.

Best,

Laird

[ochaloup]

HI ljnelson,

the dependency you refer (org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec) contains only JCA interfaces based on the Java EE specification. This dependency is brought by the Narayana spi (GitHub - jbosstm/jboss-transaction-spi: SPI for integrating the narayana transaction service ). That's mainly used for integration with WildFly app server. Nevertheless the Narayana SPI interfaces are used through the codebase. The jca api dependency is used to handle JCA inflow transactions namely it uses interface XATerminator.

I'm not sure I'm worried that the jca api interface could be needed by Narayana during processing. Even if you do not plan to use features of JCA inflow transactions or EJB remoting context propagation there could be transitive dependency touching the jca api.

[ljnelson]

Perfect answer; thanks.