[
https://jira.jboss.org/browse/JBAS-8392?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan resolved JBAS-8392.
----------------------------------
Fix Version/s: 6.0.0.M5
(was: 6.0.0.CR1)
Resolution: Done
org.jboss.as.javaee.SimpleJavaEEModuleInformer#getModulePath returns
incorrect module name for toplevel non-ear deployments
---------------------------------------------------------------------------------------------------------------------------
Key: JBAS-8392
URL:
https://jira.jboss.org/browse/JBAS-8392
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: 6.0.0.M4
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.0.0.M5
The JavaEEModuleInformer specifies this requirement for getModulePath():
/**
* Obtain the relative path of the deployment unit within the JavaEE application
* or base deployment directory.
* The deployment unit is either a JavaEE module or a component of the JavaEE module.
* If the JavaEE module is part of a JavaEE application return the relative
* path within the JavaEE application otherwise it is considered a stand alone
deployment
* and return the relative path within the base deployment directory.
* Note that the relative path includes the module name, for example
'lib/bar.jar'.
*
* @param deployment the deployment unit of the module or a component
* @return the relative path of the JavaEE module
*/
String getModulePath(DeploymentUnit deploymentUnit);
However the current implementation in SimpleJavaEEModuleInformer has this:
public String getModulePath(DeploymentUnit unit)
{
return unit.getRelativePath();
}
This incorrectly returns an empty string for a toplevel non-ear deployment (for ex: a
standalone .war deployment).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira