Changing default JNDI namming pattern for deployed ear

[najgor]

Default JNDI naming prefix is equal to EAR name.
Can I change that but in the scope of deployed and included JAR that contains many ejb components? I do not want to put the jndi name inside each component source file, i just wish to modify some of jar's config file to set this prefix.

Is this possible?

Thanx in advance.

[vianney]

Same need.

We want to be able to name our ear file with a version number like application-1.3.5.ear but if we do that we'll have to change our source code (actually just the web.xml where we define a context-param for this jndi prefix but still).

Is there anything similar to context-root for webapps?

Thx for your help,

Vianney

[apill]

I have exactly the same question.

If someone has the answer it would be very helpful.

It is not very nice having to remember to update jndi lookup code for every release.

[voidhawc]

Same here.

Different versions have a different ear name. any body know of any solutions. Don't want to update teh JNDI lookup every time.

Thanks

Grant

[voidhawc]

Hey guys,

Try @RemoteBinding(jndiBinding="location")

It's a JBoss annotation for specifying the remote interface location for EJB3.

Good luck.

Grant

[apill]

You will probably be interested in the outcome of my discussion with Bill Burke on this topic. See the following thread and jira issue.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=84259

http://jira.jboss.com/jira/browse/EJBTHREE-617