Hi Jochen,
Sent from my iPhone
> On 27 Jul 2016, at 07:47, jochenw wrote:
>
> Hi Tim,
>
> the transaction control service sounds interesting. I haven't found some
> example or tutorial which shows how to used it with JPA. Do you know whether
> something like
Hi Tim,
the transaction control service sounds interesting. I haven't found some
example or tutorial which shows how to used it with JPA. Do you know whether
something like this exists? Would be helpful to get started. I'm sure that
the documentation pages contain all relevant information, but
Hi Tim,
you should create such a feature in the tx-control code in Aries. For
example the Aries jpa code already has such a feature now.
This allows people to install their desired version independently from
the karaf version.
As soon as you have this feature I can then add it to the karaf
The depend-on flag on the bean element can be used for that.
The JPA 2.x Aries bundles should solve the service dependency problem and
be better integrated with the pax-jdbc config stuff.
2016-07-11 9:37 GMT+02:00 jochenw :
> Hello,
>
> start levels have been
Hi Timothy,
sounds interesting. Is there a description which Karaf features to use to
replace the "transaction" feature? Since we already are pretty close to a
release date, we'd rather like not to change code. However, it might be naiv
to think that such an easy exchange is possible - I haven't
Hi Jochen,
You’re absolutely right that start levels (and startup ordering) are
anti-patterns in OSGi.
It’s also the case that Aries Transaction and older versions of Aries JPA (the
1.x releases) are really hard to use. Aries JPA 1.x does not always wait
correctly for the datasources that it
Could you give a bit more information on how your persistence bundle is
used ?
The EntityManager / EntityManagerFactory should only be available in the
OSGi registry once everything is ready...
2016-07-11 9:37 GMT+02:00 jochenw :
> Hello,
>
> start levels have
Hello,
start levels have been removed for a number of bundles in the Karaf
enterprise features. In principle a good idea (sometimes start levels are
even seen as anti-pattern in OSGi).
However, sometimes I now face the issue that the transaction service is
missing when one of my persistence