I found this issue shortly after the commit. We can theoretically
release 1.0.1 at any time. I propose we wait 2 or three more weeks to
see if other issues are found.
Christian
On 07.02.2017 17:18, Matt Bellinger wrote:
When updating from a 0.10.0-SNAPSHOT version of pax-jdbc-config to the
1.0.0 release version, I noticed we were no longer able to get a
connection to our database. Upon investigating, I noticed that the
PooledDataSourceFactory service provided by pax-jdbc-pool-hikaricp did
not set the xa property. The pax-jdbc-config DataSourceConfigManager
specifically looks for xa=true or xa=false in the service filter.
This means that the ServiceTracker 'misses' the service, and is
unable to continue with the configuration of the database.
I see that this was fixed in the commit below, but I believe that
commit missed 1.0.0.
https://github.com/ops4j/org.ops4j.pax.jdbc/commit/40372375f579d2c45d09e35d1549b39a60ebc553
Is there a time frame for when this commit would make it to a released
version?
Thanks,
~Matt
--
--
------------------
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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.
