Little more information if this will help. When I deploy application1.ear
(actually name is back-local.ear), no errors and everything runs correctly.
When I deploy application2.ear (shop-local.ear) and app1 is already deployed, I
get the following error. However, I can still access my applicat
ok - last piece of information and I'm out of ideas:
Also, I am runing the latest EJB JEMS and the latest CVS Seam.
When I go look at jmx-console I find two persistent unit listed:
* ear=backoffice-local.ear,jar=backoffice-local.jar,unitName=em
* ear=shop-local.ear,jar=shop-local.jar,un
I've looked around a bit more; but haven't found anything. It seems like I
shoud be able to deploy the same persistent.xml in different ears files.
Any thoughts?
--jc
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967616#3967616
Reply to the post :
http:
The name there's gotta be unique :/ Everything else in your persistence.xml
can remain the same, and you may use just the one DS file.
If you'd like to only have one instance of your persistence.xml file, consider
repackaging such that both of your Seam apps will have access to it...
S,
ALR
"ALRubinger" wrote :
| If you'd like to only have one instance of your persistence.xml file,
consider repackaging such that both of your Seam apps will have access to it...
|
ALR,
Thanks for the information. I didn't realize that the persistence unit name
had to be unique across ears.
Yep; you can see the entry for your persistence.xml name in the JMX Console
under the heading "persistence.units"...
As far as repackaging - you have a couple options:
Deployment Isolation - Every archive into your deploy directory exists in its
own little bubble with its own classloader. Clas
Oh, the notes above are operating under the assumption that you have shared
code/libraries in your Seam apps that you might like to externalize. The
Persistence Unit should be available to all of your apps once deployed
regardless of the deployment isolation type selected.
View the original po
"connerjohn" wrote : "ALRubinger" wrote :
| | If you'd like to only have one instance of your persistence.xml file,
consider repackaging such that both of your Seam apps will have access to it...
| |
|
| ALR,
|
| Thanks for the information. I didn't realize that the persisten
This is what has to be unique:
|
|
The unit name does not have to be unique between EARs.
Why is this happening? the jboss.entity.manager.factory.jndi.name binds to
global JNDI.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968267#396826
"[EMAIL PROTECTED]" wrote : This is what has to be unique:
|
|
| |
| |
|
| The unit name does not have to be unique between EARs.
|
| Why is this happening? the jboss.entity.manager.factory.jndi.name binds to
global JNDI.
|
|
Ok - so after thinking about
"[EMAIL PROTECTED]" wrote : This is what has to be unique:
|
|
| |
| |
|
| The unit name does not have to be unique between EARs.
|
|
Stand very corrected.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968276#396827
Is there any way to bind the jndi name to a scope localised to the ear it is
within?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973538#3973538
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973538
_
Or, instead of doing the following...
| @PersistenceContext(unitName="myUnit")
| EntityManager em;
|
can I look up the EntityManager from within a session bean by its
persistence-unit name instead of via its jndi binding name?
Thanks.
Adrian
View the original post :
http://www.jboss.c
13 matches
Mail list logo
