you mean for default EJB JNDI names? No, there is not. Please log a jira feature request.
Are you saying ...
I cannot deploy an ear file named my-app-1.0.ear containing MyBean to the following JNDI path
instead it will default to
If that is what you are saying, then we are on the same wavelength and I'll raise a feature request!
Which JBoss JIRA project should I raise the feature in?
EJB3 is fine I guess. I'm not sure when we could get to this as another JBoss 4.0.x release isn't scheduled for awhile and I think this requires changes to the EAR deployer.
Log in in the EJBThree module
Has this feature request been created already? I want to vote for it! :-)
I am wondering where this feature, of prepending the .ear package name to the EJB names, is coming from. Is it in the specs of EJB 3 or JavaEE 5?
Because I see a few problems that may occur in this approach. (Or is there already a solution that I missed?)
- Maven builds & version numbers
As mentioned in the first post, EJB clients will need to know the version of the ear before being able to lookup the beans.
Moreover, new versions of .ear containing EJBs will also require updated clients (external war or client app)
- Maven builds & unit testing with embedded EJB3
JNDI names will be different between unit tests from maven using embedded EJB3 and deployment on JBoss AS afterwards.
What if the person responsible for deployment renames the .ear file before deploying? Application will not work?
Thanks for your feedback