ejb-link doesn't work in deployment

Logged In: YES
user_id=176671

it seems you forgot the attachment, at least I can't see it
in the report ATM.

anyways, this is related to bug #629145 which i'm currently
working on, see

https://sourceforge.net/tracker/?func=detail&aid=629145&group_id=22866&atid=376685

for more information.

have a fix for this in hand, just need to get around to add
a testcase to the testsuite.

Logged In: YES
user_id=665462

Am sending the Word document separately - my
attachment may have been too large for SourceForge to
accept.

Logged In: YES
user_id=665462

Document attached (hopefully)

Logged In: YES
user_id=176671

besides the Word document, can you also attach the .ear (or
a stripped down version containing the Bean in question, a
sample servlet calling the bean and the according Deployment
Descriptors)?

I have just comitted a test-case for bug #629145 to CVS
HEAD, the test works with my patch in place (which has not
been comitted yet) and I want to see if my patch fixes your
problem, too before comitting and backporting to 3.2 and 3.0
branches.

Logged In: YES
user_id=665462

I will try to send you the complete EAR.

If this doesn't get through, I will need to build a bespoke
EAR, which will take time.

Logged In: YES
user_id=176671

apparently the .ear didn't make it into the attachment, pls.
send it to me via e-mail: lqd@users.sourceforge.net

thanks

Logged In: YES
user_id=665462

Sample EAR file sent by separate e-mail.

I have tested that this deploys.

Logged In: YES
user_id=176671

i have commited a fix for this in CVS HEAD. could you please
re-check against CVS HEAD and tell me if it solves your
problem; if it does I will backport it into 3.0 and 3.2
respectively.

Logged In: YES
user_id=176671

Backported the fix to Branch_3_2, still looking into 3.0.

Logged In: YES
user_id=176671

fixed in 3.0 series. Will be in JBoss 3.0.7 release

Logged In: YES
user_id=737003

There is a bug when ejbjar is not a jar but a directory.
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[] {target},
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[] {URL.class.getName()}
);
}
<<==
}
catch( Exception e )
{
log.error( "Got Exception when looking for
DeploymentInfo: " + e );
return null;
}

Logged In: YES
user_id=176671

you mean a case where your .ear file contains an exploded
EJB .jar file?

Logged In: YES
user_id=737003

yes

Logged In: YES
user_id=176671

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

Logged In: YES
user_id=737003

Feature request 706850 added