[ https://jira.jboss.org/jira/browse/JBAS-7644?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-7644: ----------------------------------- Fix Version/s: JBossAS-6.0.0.M3 (was: JBossAS-6.0.0.M2) Priority: Critical (was: Major) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7644?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-7644: ----------------------------------- Summary: Enforce EE 6 module name requirements within an application (was: Enforce unique names for EE modules within an application) Description: Implement following from EE8.1.1: All Java EE modules have a name. The name can be explicitly set in the deployment descriptor for the module. If not set, the name of the module is the pathname of the module in the ear file with any filename extension (.jar, .war, .rar) removed, but with any directory names included. The name of a module must be unique within an application. If and only if the name is not unique (e.g., because two names are identical after removing different filename extensions) the deployment tool may choose new unique names for any of the conflicting modules; module names that do not conflict must not be changed. The algorithm for choosing unique names in such a case is product specific. Also implement this related bit from EE.8.1.2: Similarly, when a stand-alone module is deployed.... The module name can be explicitly set in the module deployment descriptor. If not set, the name of the module is the base name of the module file with any extension (.war, .jar, .rar) removed and with any directory names removed. was: Implement following from EE8.1.1: All Java EE modules have a name. The name can be explicitly set in the deployment descriptor for the module. If not set, the name of the module is the pathname of the module in the ear file with any filename extension (.jar, .war, .rar) removed, but with any directory names included. The name of a module must be unique within an application. If and only if the name is not unique (e.g., because two names are identical after removing different filename extensions) the deployment tool may choose new unique names for any of the conflicting modules; module names that do not conflict must not be changed. The algorithm for choosing unique names in such a case is product specific. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7644?page=com.atlassian.jira.plug... ] Carlo de Wolf reopened JBAS-7644: --------------------------------- standard config is missing the ModuleNameDeployer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7644?page=com.atlassian.jira.plug... ] Brian Stansberry commented on JBAS-7644: ---------------------------------------- Sorry about that. Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira