[jira] Updated: (GERONIMO-3199) Prefix ear name in deployment-id to make it unique

2007-07-27 Thread Prasad Kashyap (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Kashyap updated GERONIMO-3199:
-

Fix Version/s: 2.0.x

> Prefix ear name in deployment-id to make it unique
> --
>
> Key: GERONIMO-3199
> URL: https://issues.apache.org/jira/browse/GERONIMO-3199
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.0-M5, 2.0-M6
>Reporter: Prasad Kashyap
>Assignee: David Blevins
> Fix For: 2.0.x
>
>
> In 2.0-M3, when a bean was deployed, it's deployment-id was prefixed with 
> geronimo-deploymentUtil9638.tmpdir
> Eg: deployment-id=geronimo-deploymentUtil9638.tmpdir/SimpleStatelessSession
> This ensured a unique ID even if beans from across apps had the same name.
> Now, the deployment-id is prefixed with the name of the jar to which the bean 
> belongs to.
> Eg: deployment-id=ejb.jar/SimpleStatelessSession
> This eliminates the deployment of another app having a bean with the same 
> name packaged in a same named jar.
> http://www.nabble.com/Naming-conflict-when-deploying-testsupport-EARs-tf3834600s134.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-3199) Prefix ear name in deployment-id to make it unique

2008-07-23 Thread Joe Bohn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Bohn updated GERONIMO-3199:
---

Fix Version/s: (was: 2.0.x)
   2.0.1

> Prefix ear name in deployment-id to make it unique
> --
>
> Key: GERONIMO-3199
> URL: https://issues.apache.org/jira/browse/GERONIMO-3199
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.0-M5, 2.0-M6
>Reporter: Prasad Kashyap
>Assignee: David Blevins
> Fix For: 2.0.1
>
>
> In 2.0-M3, when a bean was deployed, it's deployment-id was prefixed with 
> geronimo-deploymentUtil9638.tmpdir
> Eg: deployment-id=geronimo-deploymentUtil9638.tmpdir/SimpleStatelessSession
> This ensured a unique ID even if beans from across apps had the same name.
> Now, the deployment-id is prefixed with the name of the jar to which the bean 
> belongs to.
> Eg: deployment-id=ejb.jar/SimpleStatelessSession
> This eliminates the deployment of another app having a bean with the same 
> name packaged in a same named jar.
> http://www.nabble.com/Naming-conflict-when-deploying-testsupport-EARs-tf3834600s134.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-3199) Prefix ear name in deployment-id to make it unique

2008-09-02 Thread Donald Woods (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods updated GERONIMO-3199:
---

Fix Version/s: (was: 2.0.1)

> Prefix ear name in deployment-id to make it unique
> --
>
> Key: GERONIMO-3199
> URL: https://issues.apache.org/jira/browse/GERONIMO-3199
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.0-M5, 2.0-M6
>Reporter: Prasad Kashyap
>Assignee: David Blevins
>
> In 2.0-M3, when a bean was deployed, it's deployment-id was prefixed with 
> geronimo-deploymentUtil9638.tmpdir
> Eg: deployment-id=geronimo-deploymentUtil9638.tmpdir/SimpleStatelessSession
> This ensured a unique ID even if beans from across apps had the same name.
> Now, the deployment-id is prefixed with the name of the jar to which the bean 
> belongs to.
> Eg: deployment-id=ejb.jar/SimpleStatelessSession
> This eliminates the deployment of another app having a bean with the same 
> name packaged in a same named jar.
> http://www.nabble.com/Naming-conflict-when-deploying-testsupport-EARs-tf3834600s134.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.