tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENEJB-1439) The link resolving code shouldn't be using the moduleId, rather the path of the archive itself.
Date Tue, 08 Mar 2011 15:15:59 GMT

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

Shawn Jiang updated OPENEJB-1439:
---------------------------------

    Attachment: 0001-OPENEJB-1439-The-link-resolving-code-shouldn-t-be-us.patch

> The link resolving code shouldn't be using the moduleId, rather the path of the archive
itself. 
> ------------------------------------------------------------------------------------------------
>
>                 Key: OPENEJB-1439
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1439
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: general
>            Reporter: Shawn Jiang
>         Attachments: 0001-OPENEJB-1439-The-link-resolving-code-shouldn-t-be-us.patch
>
>
> ejb link cases can't pass after we removed the extension from the moduleId.  
> we need the .jar style module package name to resolve the EJB link(xxx.jar#xxx).  The
link resolving code shouldn't be using the moduleId, rather the path of the archive itself.
   see [1] for details.
> [1]http://apache-geronimo.328035.n3.nabble.com/Can-anyone-tell-me-what-s-the-reason-to-remove-the-jar-extension-in-GERONIMO-5253-td2644435.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message