"rdewell" wrote : I guess I always (incorrectly) assumed that JNDI lookups were
automatically isolated to the EAR that I'm "in" -- by nature preventing any
conflicts across EARs...
ENC lookups are isolated. Not global JNDI lookups.
"rdewell" wrote : It's weird to me that by default multiple EAR
"jay_stramel" wrote : So is there any way around hard coding ear names into our
look ups?
Sure. You can define a mapping of the global JNDI name into the ENC. (This
requires vendor specific metadata, unfortunately; something that needs to be
fixed in a future rev of EJB.)
But actually, with Se
I guess I always (incorrectly) assumed that JNDI lookups were automatically
isolated to the EAR that I'm "in" -- by nature preventing any conflicts across
EARs...
It's weird to me that by default multiple EARs share the same class / name
lookup space.
View the original post :
http://www.jbos
So is there any way around hard coding ear names into our look ups?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922626#3922626
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922626
-
You always need the name of the EAR. That is because it is perfectly valid and
indeed common to have the same bean in multiple EARs.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922542#3922542
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
Does that mean that if you specify the name with the annotation that the jar
name isn't needed to look it up?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922487#3922487
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=
huh? So different "versions" lived in different packages?
This is a very, very strange thing, surely?
What is so hard about
@Stateful(name="qualifiedName")
in these kind of strange cases?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922471#3922471
Reply
Although I can see how it was broken for that particular case, the JNDI change
has made things much more difficult for many other cases.
The application I'm working on is comprised of many different deployables and
each one has a version number that changes over time. I'm not even sure how to
Note that I asked for this change in EJB3 because we had a major problem where
Seam apps would not deploy alongside each other because the same local
interface existed in multiple EARs.
So the old way was much more broken.
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
I think it is *extremely* uncommon to have to session beans with the same EJB
name in the same EAR.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922463#3922463
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922463
10 matches
Mail list logo
