aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giuseppe Gerla <>
Subject Re: Prototype for a new aries jpa impl
Date Thu, 02 Apr 2015 16:48:42 GMT
Hi Christian
I would be very interested to try the new prototype, but I have few time.
So before I start, I would like to ask you:
1. you say that the current code is not yet complete. What is missing? What
functionalities I will not test?
2. Is it possible or it will be possible to set some properties to the EMF?
(something like jpa:map functionality. See

Thanks for your work

2015-04-02 15:41 GMT+02:00 Christian Schneider <>:

> I am experimenting for some time with a new way to implement jpa support.
> You can find the design on this website:
> The prototype code is at:
> The goals for the new design are:
> - Simpler and more robust implementation using OSGi service dynamics.
> Tracking all dependencies and publishing / unpublishing
> EntityManagerFactory when any go away
> - Move some functionality to other projects like wrapping XA DataSources
> to pax-jdbc.
> - Support for other frameworks like declarative services using JPATemplate
> and closures
> The current code is not yet complete but already works for blueprint and
> DS.
> I would be happy about any feedback.
> Especially I would be interested if with the new approach Quiesce is still
> necessary. The code already makes sure that the EntityManagerFactory is
> nicely cleaned up. EntityManagers are only held for the duration of a
> request. So if blueprint Quiesce shuts down the requests then I think the
> jpa impls should not need to do additional work here. I tested to update
> all modules at runtime and all seems to work nicely. With the current aries
> jpa I can not update the persistence unit bundles. See
> Christian
> --
> Christian Schneider
> Open Source Architect

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message