Yes. I think I added the transaction feature as the postgres driver
imports the javax.transaction.xa package.
Recently I discovered that another way to make it deployable is to just
provide the javax.transaction spec bundle with dependency="true".
This allows the feature to deploy while not tying it to the Aries
transaction manager. The dependency="true" allows karaf to even replace
the spec bundle if it has a better alternative.
Should we change it like that?
Christian
On 22.11.2016 13:49, Sascha Vogt wrote:
Hi,
Not sure as I haven't written the feature, but have you looked into the
headers of the Postgres driver? I see a non-optional
"javax.transaction.xa" import in there. Without that the driver probably
will not resolve -> hence the requirement to the transaction feature.
Of course if you deploy a bundle yourself which contains those
transaction-exports then you can use it without the feature. On the
other hand: The feature only contains the driver. Without any wrapping,
so if you handle the rest yourself, why using the feature at all?
Greetings
-Sascha-
Am 17.11.2016 um 19:28 schrieb Сергей Капралов:
Hello,
I wonder why "pax-jdbc-postgresql" Karaf feature strictly depends on
"transaction" feature? I believe I can gladly use "pax-jdbc-postgresql"
without being dependent on Aries Transaction manager.
https://github.com/ops4j/org.ops4j.pax.jdbc/blob/master/pax-jdbc-features/src/main/resources/features.xml#L86
Is it a bug?
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
