You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Shawn Jiang (JIRA)" <ji...@apache.org> on 2011/03/13 04:03:59 UTC
[jira] Created: (OPENEJB-1445) We should provide moduleUri in
contextData as well when generating the deploymentId after the changes in
OPENEJB-1442
We should provide moduleUri in contextData as well when generating the deploymentId after the changes in OPENEJB-1442
---------------------------------------------------------------------------------------------------------------------
Key: OPENEJB-1445
URL: https://issues.apache.org/jira/browse/OPENEJB-1445
Project: OpenEJB
Issue Type: Bug
Components: deployment
Affects Versions: (trunk/openejb3)
Reporter: Shawn Jiang
Previously, we only have moduleId in the contextData to generate the deploymentId in
org.apache.openejb.config.InitEjbDeployments.deploy(EjbModule, Map<String, String>, Set<String>)
After the fixes in OPENEJB-1442, moduleUri becomes a important element of deploymentId in most of the cases. We should provide moduleUri in contextData as well
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OPENEJB-1445) We should provide moduleUri in
contextData as well when generating the deploymentId after the changes in
OPENEJB-1442
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006332#comment-13006332 ]
Shawn Jiang commented on OPENEJB-1445:
--------------------------------------
There are many openejb document on how to configure the deploymentId with modueId. We might also want to update these documents after the changes in OPENEJB-1442
> We should provide moduleUri in contextData as well when generating the deploymentId after the changes in OPENEJB-1442
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: OPENEJB-1445
> URL: https://issues.apache.org/jira/browse/OPENEJB-1445
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: (trunk/openejb3)
> Reporter: Shawn Jiang
> Fix For: 3.2
>
> Attachments: 0001-OPENEJB-1445.patch
>
>
> Previously, we only have moduleId in the contextData to generate the deploymentId in
> org.apache.openejb.config.InitEjbDeployments.deploy(EjbModule, Map<String, String>, Set<String>)
> After the fixes in OPENEJB-1442, moduleUri becomes a important element of deploymentId in most of the cases. We should provide moduleUri in contextData as well
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (OPENEJB-1445) We should provide moduleUri in
contextData as well when generating the deploymentId after the changes in
OPENEJB-1442
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan resolved OPENEJB-1445.
---------------------------
Resolution: Fixed
Fix Version/s: 3.2
Commit changes to trunk at rev 1081260
> We should provide moduleUri in contextData as well when generating the deploymentId after the changes in OPENEJB-1442
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: OPENEJB-1445
> URL: https://issues.apache.org/jira/browse/OPENEJB-1445
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: (trunk/openejb3)
> Reporter: Shawn Jiang
> Fix For: 3.2
>
> Attachments: 0001-OPENEJB-1445.patch
>
>
> Previously, we only have moduleId in the contextData to generate the deploymentId in
> org.apache.openejb.config.InitEjbDeployments.deploy(EjbModule, Map<String, String>, Set<String>)
> After the fixes in OPENEJB-1442, moduleUri becomes a important element of deploymentId in most of the cases. We should provide moduleUri in contextData as well
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OPENEJB-1445) We should provide moduleUri in
contextData as well when generating the deploymentId after the changes in
OPENEJB-1442
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated OPENEJB-1445:
---------------------------------
Attachment: 0001-OPENEJB-1445.patch
> We should provide moduleUri in contextData as well when generating the deploymentId after the changes in OPENEJB-1442
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: OPENEJB-1445
> URL: https://issues.apache.org/jira/browse/OPENEJB-1445
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: (trunk/openejb3)
> Reporter: Shawn Jiang
> Attachments: 0001-OPENEJB-1445.patch
>
>
> Previously, we only have moduleId in the contextData to generate the deploymentId in
> org.apache.openejb.config.InitEjbDeployments.deploy(EjbModule, Map<String, String>, Set<String>)
> After the fixes in OPENEJB-1442, moduleUri becomes a important element of deploymentId in most of the cases. We should provide moduleUri in contextData as well
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira