In the 3.1 release changelog I could see :
EAR-style classpath application discovery groups individual modules as
an EAR allowing sharing of persistence units and improved connector
and custom MDB deployment.
Did it what we discussed in this thread ?
That's actually a different feature.
Could it be done for 3.1 release ?
Hi to all,
In the 3.1 release changelog I could see :
EAR-style classpath application discovery groups individual modules as
an EAR allowing sharing of persistence units and improved connector
and custom MDB deployment.
Did it what we discussed in this
On Oct 28, 2008, at 2:08 AM, Henri Gomez wrote:
Could it be done for 3.1 release ?
Hi to all,
In the 3.1 release changelog I could see :
EAR-style classpath application discovery groups individual modules as
an EAR allowing sharing of persistence units and improved connector
and custom MDB
Any news about this request ?
Could it be done for 3.1 release ?
Thanks
Le 16 oct. 08 à 12:13, Maxime Thieu [EMAIL PROTECTED] a écrit :
Hi David,
Thanks for your anwser.
I allready try including persistence.xml in my webapp.
But this doesn't works because I have Service in service.jar
Hello everybody,
I am developping ejb-jar module (let's call it service.jar) which contains
EJB, Entity, Service and persistence.xml (in META-INF).
I am developping webapp module (let's call it test.war) which contains
Servlets who are calling some Service in service.jar (using entityManager to
Hi Maxime,
It should be possible to put the service.jar in the Tomcat lib/
directory without a persistence.xml in it and then include that
persistence xml in your webapp. You should be able to include a jar-
file element in the unit declaration that points to the C:/tomcat6/
Not entirely sure though if that's really what you're after. We don't
currently have any support for global persistence units. Meaning say a
persistence unit declared outside of an ear at server level and available to
all ears/apps deployed. It might be something we could add if that's
