[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-617) Ability to configure the root context of a deployed ear.

[Torben Jaeger (JIRA)]

     [ http://jira.jboss.com/jira/browse/EJBTHREE-617?page=all ]

Torben Jaeger updated EJBTHREE-617:
-----------------------------------

    Attachment: ejbthree-617.patch

consolidated unit test

> Ability to configure the root context of a deployed ear.
> --------------------------------------------------------
>
>                 Key: EJBTHREE-617
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-617
>             Project: EJB 3.0
>          Issue Type: Feature Request
>            Reporter: Adrian Pillinger
>         Attachments: ejbthree-617.patch, ejbthree-617.patch
>
>
> Currently, if you deploy an ear named my-ear-1.2.1.ear, containing an EJB3 archive, which contains an EJB named MyBean it will deploy the remote interface to a JNDI name similar to:
> my-ear-1.2.1/MyBean/remote
> This can be nasty since client has to be updated each release to point to the correct JNDI name.
> To remedy this, a feature that allows configurability of the base portion of the JNDI name within the ear file, like the application.xml that provides the configuration of the root context for web apps.
> Basically, the functionality would allow the EJB to be configured to deploy to the following JNDI name, for examlpe
> my-ear/MyBean/remote

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira