[jira] (MEAR-181) Adding ejb-ref in application.xml

["Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MEAR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl-Heinz Marbaise updated MEAR-181:
-------------------------------------

    Fix Version/s: 2.10

> Adding ejb-ref in application.xml
> ---------------------------------
>
>                 Key: MEAR-181
>                 URL: https://jira.codehaus.org/browse/MEAR-181
>             Project: Maven Ear Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.9
>            Reporter: Byte Schubser
>             Fix For: 2.10
>
>
> It's great to be capable of generating an application.xml when building an ear. But I do have application local jndi names that should be assigned to the correct one during building the application. There are technical components that don't know their destination at build time. But when packaging the ear the destination is known. So I want to redirect application local names.
> My Scenario:
> I want to prevent the deployment when a required service is not available in the required version in a multiple versions per ear scenario. (The jndi name of the required service depends on the version number of the api that is used within the ear)
> e.g. java:app/serviceXYZ-> java:global/ear/module/serviceXYZ
> <ejb-ref>
>   <ejb-ref-name>java:app/serviceXYZ</ejb-ref-name>
>   <ejb-ref-type>Session</ejb-ref-type>
>   <lookup-name>java:global/ear/module/serviceXYZ</lookup-name>
> </ejb-ref>
> I'd really appreciate to be able to add ejb-refs to when generating an application.xml
> Thanks



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)