It sounds good, and it's what I leverage in karaf-boot (with the @jpa
annotation which creates the persistence.xml for you).
Regards
JB
On 09/16/2015 11:05 AM, Christian Schneider wrote:
Hi Jochen,
yes this is correct. Aries JPA 2 only uses the annotations.
In addition I am currently working on a new Aries Transaction 3 that
will then also only use the jta 1.2 annotations.
This means that the whole JPA/JTA setup will then be based on the
standard set of annotations. The advantage is that you do not need any
Aries specific imports in your bundle.
I will also release a new maven-blueprint-plugin version that is adapted
for the new JPA and JTA versions and creates the blueprint xml from CDI
+ JEE annotations. So in the end you can use blueprint with almost the
same set of annotations like JEE.
Christian
On 16.09.2015 10:50, jochenw wrote:
Does this mean that now it is *mandatory *to define the persistence
unit per
annotation, and it is no longer possible to define it in the blueprint
file?
Is this a bug of a feature? Or, in other words, does it make sense to
open a
Jira for Aries if I want to get the blueprint.xml mechanism back (the
respective entries seem to be missing in the xsd file)?
Best Regards,
Jochen
--
View this message in context:
http://karaf.922171.n3.nabble.com/Bundle-is-waiting-for-namespace-handlers-http-aries-apache-org-xmlns-jpa-v1-0-0-tp4042275p4042618.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
