-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
native builds fail unless narayana-jta is also present #108
Comments
I have to add |
…g.jboss:jboss-transaction-spi
…g.jboss:jboss-transaction-spi (quarkiverse#111)
…a and org.jboss:jboss-transaction-spi (quarkiverse#111)" This reverts commit 8b97af8.
…a and org.jboss:jboss-transaction-spi (quarkiverse#111)" This reverts commit 8b97af8.
Its not clear to me that graal issue actually applies since the transaction settings are runtime configurable. The wrapper class is always loaded, and so the XA related code within it and thus all the XA related classes would still be considered reachable at runtime because it really is. It doesnt seem like that graal issue is being worked on any time soon regardless, and having the XA bits be required and present even when not being used feels a bit icky. An alternative solution would be to indirect the use of the transaction related classes such that it is isolated to a support class that is normally used, but we can add substitutions to disable it from being reachable in cases its known the transaction classes arent present during the native build, meaning they then arent actually required when not actually being used. I've taken a shot at that in #113 |
* allow manually running the tests, useful for branches * Revert "Fix #108 to add org.jboss.narayana.jta:narayana-jta and org.jboss:jboss-transaction-spi (#111)" This reverts commit 8b97af8. * indirect transaction bits, enable native builds when XA RecoveryRegistry etc classes/deps are not present or being used
…e#113) * allow manually running the tests, useful for branches * Revert "Fix quarkiverse#108 to add org.jboss.narayana.jta:narayana-jta and org.jboss:jboss-transaction-spi (quarkiverse#111)" This reverts commit 8b97af8. * indirect transaction bits, enable native builds when XA RecoveryRegistry etc classes/deps are not present or being used
* allow manually running the tests, useful for branches * Revert "Fix #108 to add org.jboss.narayana.jta:narayana-jta and org.jboss:jboss-transaction-spi (#111)" This reverts commit 8b97af8. * indirect transaction bits, enable native builds when XA RecoveryRegistry etc classes/deps are not present or being used Co-authored-by: Robbie Gemmell <robbie@apache.org>
The quarkus-pooled-jms deployment module has an optional dependency on quarkus-narayana-jta-deployment (with the XA support for the pooling being disabled by default), however it appears the extension really requires some bits from it be present. A native application build using quarkus-pooled-jms, not doing any XA at all, fails without it due to class org.jboss.tm.XAResourceRecoveryRegistry not being found:
(For more complete stack, see later)
This was noticed simple adding the quarkus-pooled-jms 2.0.0 dependency to an application using quarkus-qpid-jms 2.0.0, building with Mandrel 22.3.2.0 . Not even actually using the pool yet. Adding the dependency on quarkus-narayana-jta-deployment to the application itself, even though it wasnt doing any XA, was required to get the build to work with quarkus-pooled-jms in place.
More complete stacks:
The text was updated successfully, but these errors were encountered: