[
https://issues.apache.org/jira/browse/TOMEE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinis Vicups resolved TOMEE-505.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
A more sensual default setting is introduced in current snapshot, thus this is
resolved.
> 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
> Fix For: 1.6.0
>
>
> 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
