Details
-
Feature Request
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
None
Description
SourceForge Submitter: vancan13 .
(see [ jboss-Bugs-650929 ] ejb-link doesn't work in
deployment)
There is a bug when ejbjar is not a jar but a directory
(when .ear file contains exploded EJB .jar files).
An additional '/' must be added to the ejbjar URL.
You can add in the method "resolveRelativeLink" of
"EjbUtil.java" the following code:
DeploymentInfo targetInfo = null;
try
{
targetInfo = (DeploymentInfo)server.invoke(
MainDeployerMBean.OBJECT_NAME,
"getDeployment",
new Object[]
new String[] {URL.class.getName()}
);
==>>
// if null, try with an extra '/'
// (happen when ejbjar is a directory)
if( targetInfo == null )
{
// add a '/' at the end and retry
target = new URL( ourPath + '/' );
targetInfo = (DeploymentInfo)server.invoke(
MainDeployerMBean.OBJECT_NAME,
"getDeployment",
new Object[] {target}
,
new String[]
);
}
<<==
}
catch( Exception e )
==>>>>>>>>>>>>>>
>Comment By: Christian Riege (lqd)
personally i think this is out of the scope of the specs as
the specs don't mention exploded modules inside of an .ear
file (or any exploded content at all). however i can see
your use-case for this.
could you please re-file this as a separate "Feature
Request" here on sourceforge and i'll integrate it (yeah,
sounds like bureaucracy but i want to keep track of it
separately from this bug).
thanks in advance,
christian