EARContentsDeployer creates the wrong name for modules ------------------------------------------------------ Key: JBAS-7797 URL: https://jira.jboss.org/jira/browse/JBAS-7797 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-6.0.0.M2 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M3 It passes the result of this calculation to ModuleMetaData.setFileName(): private String earRelativePath(String earPath, String pathName) { StringBuilder tmp = new StringBuilder(pathName); tmp.delete(0, earPath.length()); return tmp.toString(); } That will include a leading /, e.g. foo.ear/bar.war will have a ModuleMetaData with name "/bar.war". It should be "bar.war". This impacts the processing done as part of JBAS-7644. EARStructure has the same flaw, but the "earRelativePath" is passed to VirtualFile.getChild(earRelativePath) which ignores the leading /. -- 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