Zuerst: Danke nach Berlin!
I checked the Beans and the Beans are not a double deployment. They even deploy
once and they deploy without errors.
I think I just missed something. Maybe it's the Deployment descriptor I was not
aware of. All my both JARs have is
persitence.xml (both look the
The deployment descriptors seem not to be the problem as the EJB 3 Spec states
that it's not needed:
| Definition of the Java language metadata annotations that can be used to
annotate EJB applications.
| These metadata annotations are targeted at simplifying the developer?s
task, at
ANYWAY:
! ! ! I DO ALSO APPRECIATE DEPLOYMENT DESCRIPTOR EXAMLES ! ! !
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3985396#3985396
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3985396
So, die Lösung ist gefunden:
-Man benötigt nur einen persistence.xml - Eintrag in dem JAR mit den Entities,
die andere kann leer bleiben.
-Als Verweis benutzt man dann
|
@PersistenceContext(unitName=../NAMEDESANDERENJARS.jar#PERSISTENCEUNITNAME)
private EntityManager em;
|
Also z.B.
|
Maybe this will help anybody in an web environment (Persistence Manager is not
synchronized and not intended to use in Multithread environments)
http://weblogs.java.net/blog/ss141213/archive/2005/12/index.html
View the original post :
I've got a problem addressing a CMP bean in a different Eclipse project (the
projects should be seperated). Both projects should work fine, but when I try
to address the CMP Bean (like I do with the local beans as well) I get the
error below.
We have git two EJB projects: core-ejb and
