You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2012/10/25 13:21:12 UTC

[jira] [Commented] (TOMEE-505) OpenEJB DeploymentId improvement

    [ https://issues.apache.org/jira/browse/TOMEE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484049#comment-13484049 ] 

Romain Manni-Bucau commented on TOMEE-505:
------------------------------------------

i'm +1 on the behavior and -1 to do it now for compatibility reason

can we postpone it (for 1.6 at least for instance)?
                
> OpenEJB DeploymentId improvement
> --------------------------------
>
>                 Key: TOMEE-505
>                 URL: https://issues.apache.org/jira/browse/TOMEE-505
>             Project: TomEE
>          Issue Type: Improvement
>    Affects Versions: 1.5.1
>            Reporter: Reinis Vicups
>
> IF I have two applications running on same TomEE instance and such that they employ EJB with the identical name (e.g. in my case it is some security relevant bean used in all my apps) the deployment of the second bean will fail because the bean with the same name already exists.
> As I understand the openejb.deploymentId.format parameter has default value of {ejbName}
> I suggest to change default value to {appId}/{ejbName}, this would elegantly and generally avoid this issue?
> example: openejb.deploymentId.format = {appId}/{ejbName}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira