[
https://issues.apache.org/jira/browse/GERONIMO-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang resolved GERONIMO-6016.
-----------------------------------
Resolution: Fixed
fixed with :
ASF #1137888 Tue Jun 21 07:22:59 UTC 2011 genspring
GERONIMO-6016 Geronimo can't handle well when modules in ear has the same name.
Files Changed
> Geronimo can't handle well when modules in ear has the same name.
> -----------------------------------------------------------------
>
> Key: GERONIMO-6016
> URL: https://issues.apache.org/jira/browse/GERONIMO-6016
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0
> Reporter: Shawn Jiang
> Assignee: Shawn Jiang
>
> Basically, for following structure ear. module.jar and module.war will have
> the same java:module/ModuleName value accroding to ejb31 spec 4.4.1.
> ear
> -- module.jar
> ---module.war
> Many logic in geronimo depends on the module name so that there will be
> conflict when handling these same name modules.
> ----------------------------------------
> ejb31 spec 4.4.1
> <module-name> is the name of the module in which the session bean is
> packaged. In a stand-alone
> ejb-jar file or .war file, the <module-name> defaults to the base name of the
> module with any
> filename extension removed. In an ear file, the <module-name> defaults to the
> pathname of the
> module with any filename extension removed, but with any directory names
> included.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
