[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: James Strachan (strachancambs)
Assigned to: Christian Riege (lqd)
Summary: ejb-link doesn't work in deployment
Initial Comment:
JBoss behaviour has changed between Version 2.4.6
and Version 3.0.4.
In Version 2.4.6, a reference from a Web Archive to a
deployed EJB could be resolved using the ejb-link
attribute of the ejb-ref attribute within web.xml. No
jndi-name attribute is required from jboss-web.xml.
This behaviour has changed in Version 3.0.4.
Deploying a Web Archive with a valid ejb-link
attribute, but no jndi-name attribute, results in a
Deployment Exception.
Fuller details of the problem , and of tests carried out,
are set out in a Word document within the attached
zip file.
JBoss Version 3.0.4
OS Windows XP Home
JDK 1.4.0
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-19 18:52
Message:
Logged In: YES
user_id=737003
yes
--
Comment By: Christian Riege (lqd)
Date: 2003-03-19 18:37
Message:
Logged In: YES
user_id=176671
you mean a case where your .ear file contains an exploded
EJB .jar file?
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-18 19:03
Message:
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;
}
--
Comment By: Christian Riege (lqd)
Date: 2003-03-13 06:04
Message:
Logged In: YES
user_id=176671
fixed in 3.0 series. Will be in JBoss 3.0.7 release
--
Comment By: Christian Riege (lqd)
Date: 2003-03-07 09:11
Message:
Logged In: YES
user_id=176671
Backported the fix to Branch_3_2, still looking into 3.0.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-12 16:53
Message:
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.
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-10 10:42
Message:
Logged In: YES
user_id=665462
Sample EAR file sent by separate e-mail.
I have tested that this deploys.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-10 09:43
Message:
Logged In: YES
user_id=176671
apparently the .ear didn't make it into the attachment, pls.
send it to me via e-mail: [EMAIL PROTECTED]
thanks
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-09 19:15
Message:
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.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-09 18:09
Message:
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.
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: James Strachan (strachancambs)
Assigned to: Christian Riege (lqd)
Summary: ejb-link doesn't work in deployment
Initial Comment:
JBoss behaviour has changed between Version 2.4.6
and Version 3.0.4.
In Version 2.4.6, a reference from a Web Archive to a
deployed EJB could be resolved using the ejb-link
attribute of the ejb-ref attribute within web.xml. No
jndi-name attribute is required from jboss-web.xml.
This behaviour has changed in Version 3.0.4.
Deploying a Web Archive with a valid ejb-link
attribute, but no jndi-name attribute, results in a
Deployment Exception.
Fuller details of the problem , and of tests carried out,
are set out in a Word document within the attached
zip file.
JBoss Version 3.0.4
OS Windows XP Home
JDK 1.4.0
--
Comment By: Christian Riege (lqd)
Date: 2003-03-20 12:01
Message:
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
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-19 19:52
Message:
Logged In: YES
user_id=737003
yes
--
Comment By: Christian Riege (lqd)
Date: 2003-03-19 19:37
Message:
Logged In: YES
user_id=176671
you mean a case where your .ear file contains an exploded
EJB .jar file?
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-18 20:03
Message:
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;
}
--
Comment By: Christian Riege (lqd)
Date: 2003-03-13 07:04
Message:
Logged In: YES
user_id=176671
fixed in 3.0 series. Will be in JBoss 3.0.7 release
--
Comment By: Christian Riege (lqd)
Date: 2003-03-07 10:11
Message:
Logged In: YES
user_id=176671
Backported the fix to Branch_3_2, still looking into 3.0.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-12 17:53
Message:
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.
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-10 11:42
Message:
Logged In: YES
user_id=665462
Sample EAR file sent by separate e-mail.
I have tested that this deploys.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-10 10:43
Message:
Logged In: YES
user_id=176671
apparently the .ear didn't make it into the attachment, pls.
send it to me via e-mail: [EMAIL PROTECTED]
thanks
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-09 20:15
Message:
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.
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: James Strachan (strachancambs)
Assigned to: Christian Riege (lqd)
Summary: ejb-link doesn't work in deployment
Initial Comment:
JBoss behaviour has changed between Version 2.4.6
and Version 3.0.4.
In Version 2.4.6, a reference from a Web Archive to a
deployed EJB could be resolved using the ejb-link
attribute of the ejb-ref attribute within web.xml. No
jndi-name attribute is required from jboss-web.xml.
This behaviour has changed in Version 3.0.4.
Deploying a Web Archive with a valid ejb-link
attribute, but no jndi-name attribute, results in a
Deployment Exception.
Fuller details of the problem , and of tests carried out,
are set out in a Word document within the attached
zip file.
JBoss Version 3.0.4
OS Windows XP Home
JDK 1.4.0
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-20 12:16
Message:
Logged In: YES
user_id=737003
Feature request 706850 added
--
Comment By: Christian Riege (lqd)
Date: 2003-03-20 11:01
Message:
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
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-19 18:52
Message:
Logged In: YES
user_id=737003
yes
--
Comment By: Christian Riege (lqd)
Date: 2003-03-19 18:37
Message:
Logged In: YES
user_id=176671
you mean a case where your .ear file contains an exploded
EJB .jar file?
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-18 19:03
Message:
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;
}
--
Comment By: Christian Riege (lqd)
Date: 2003-03-13 06:04
Message:
Logged In: YES
user_id=176671
fixed in 3.0 series. Will be in JBoss 3.0.7 release
--
Comment By: Christian Riege (lqd)
Date: 2003-03-07 09:11
Message:
Logged In: YES
user_id=176671
Backported the fix to Branch_3_2, still looking into 3.0.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-12 16:53
Message:
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.
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-10 10:42
Message:
Logged In: YES
user_id=665462
Sample EAR file sent by separate e-mail.
I have tested that this deploys.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-10 09:43
Message:
Logged In: YES
user_id=176671
apparently the .ear didn't make it into the attachment, pls.
send it to me via e-mail: [EMAIL PROTECTED]
thanks
--
Comment By: James Strachan (strachancambs)
Date:
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: James Strachan (strachancambs)
Assigned to: Christian Riege (lqd)
Summary: ejb-link doesn't work in deployment
Initial Comment:
JBoss behaviour has changed between Version 2.4.6
and Version 3.0.4.
In Version 2.4.6, a reference from a Web Archive to a
deployed EJB could be resolved using the ejb-link
attribute of the ejb-ref attribute within web.xml. No
jndi-name attribute is required from jboss-web.xml.
This behaviour has changed in Version 3.0.4.
Deploying a Web Archive with a valid ejb-link
attribute, but no jndi-name attribute, results in a
Deployment Exception.
Fuller details of the problem , and of tests carried out,
are set out in a Word document within the attached
zip file.
JBoss Version 3.0.4
OS Windows XP Home
JDK 1.4.0
--
Comment By: Van caneghem (vancan13)
Date: 2003-03-18 19:03
Message:
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;
}
--
Comment By: Christian Riege (lqd)
Date: 2003-03-13 06:04
Message:
Logged In: YES
user_id=176671
fixed in 3.0 series. Will be in JBoss 3.0.7 release
--
Comment By: Christian Riege (lqd)
Date: 2003-03-07 09:11
Message:
Logged In: YES
user_id=176671
Backported the fix to Branch_3_2, still looking into 3.0.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-12 16:53
Message:
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.
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-10 10:42
Message:
Logged In: YES
user_id=665462
Sample EAR file sent by separate e-mail.
I have tested that this deploys.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-10 09:43
Message:
Logged In: YES
user_id=176671
apparently the .ear didn't make it into the attachment, pls.
send it to me via e-mail: [EMAIL PROTECTED]
thanks
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-09 19:15
Message:
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.
--
Comment By: Christian Riege (lqd)
Date: 2002-12-09 18:09
Message:
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.
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-09 18:02
Message:
Logged In: YES
user_id=665462
Document attached (hopefully)
--
Comment By: James Strachan (strachancambs)
Date: 2002-12-09 18:00
Message:
Logged In: YES
user_id=665462
Am sending the Word document
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: Christian Riege (lqd) Date: 2003-03-13 07:04 Message: Logged In: YES user_id=176671 fixed in 3.0 series. Will be in JBoss 3.0.7 release -- Comment By: Christian Riege (lqd) Date: 2003-03-07 10:11 Message: Logged In: YES user_id=176671 Backported the fix to Branch_3_2, still looking into 3.0. -- Comment By: Christian Riege (lqd) Date: 2002-12-12 17:53 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-10 11:42 Message: Logged In: YES user_id=665462 Sample EAR file sent by separate e-mail. I have tested that this deploys. -- Comment By: Christian Riege (lqd) Date: 2002-12-10 10:43 Message: Logged In: YES user_id=176671 apparently the .ear didn't make it into the attachment, pls. send it to me via e-mail: [EMAIL PROTECTED] thanks -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 20:15 Message: 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. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 19:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 17:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: Christian Riege (lqd) Date: 2003-03-07 10:11 Message: Logged In: YES user_id=176671 Backported the fix to Branch_3_2, still looking into 3.0. -- Comment By: Christian Riege (lqd) Date: 2002-12-12 17:53 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-10 11:42 Message: Logged In: YES user_id=665462 Sample EAR file sent by separate e-mail. I have tested that this deploys. -- Comment By: Christian Riege (lqd) Date: 2002-12-10 10:43 Message: Logged In: YES user_id=176671 apparently the .ear didn't make it into the attachment, pls. send it to me via e-mail: [EMAIL PROTECTED] thanks -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 20:15 Message: 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. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 19:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 17:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: Christian Riege (lqd) Date: 2002-12-12 17:53 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-10 11:42 Message: Logged In: YES user_id=665462 Sample EAR file sent by separate e-mail. I have tested that this deploys. -- Comment By: Christian Riege (lqd) Date: 2002-12-10 10:43 Message: Logged In: YES user_id=176671 apparently the .ear didn't make it into the attachment, pls. send it to me via e-mail: [EMAIL PROTECTED] thanks -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 20:15 Message: 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. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 19:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 17:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: Christian Riege (lqd) Date: 2002-12-10 10:43 Message: Logged In: YES user_id=176671 apparently the .ear didn't make it into the attachment, pls. send it to me via e-mail: [EMAIL PROTECTED] thanks -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 20:15 Message: 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. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 19:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 17:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: James Strachan (strachancambs) Date: 2002-12-10 10:42 Message: Logged In: YES user_id=665462 Sample EAR file sent by separate e-mail. I have tested that this deploys. -- Comment By: Christian Riege (lqd) Date: 2002-12-10 09:43 Message: Logged In: YES user_id=176671 apparently the .ear didn't make it into the attachment, pls. send it to me via e-mail: [EMAIL PROTECTED] thanks -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:15 Message: 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. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 18:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 16:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Nobody/Anonymous (nobody) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: Christian Riege (lqd) Date: 2002-12-09 17:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 16:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 16:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: Christian Riege (lqd) Date: 2002-12-09 19:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 17:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-650929 ] ejb-link doesn't work in deployment
Bugs item #650929, was opened at 2002-12-09 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: James Strachan (strachancambs) Assigned to: Christian Riege (lqd) Summary: ejb-link doesn't work in deployment Initial Comment: JBoss behaviour has changed between Version 2.4.6 and Version 3.0.4. In Version 2.4.6, a reference from a Web Archive to a deployed EJB could be resolved using the ejb-link attribute of the ejb-ref attribute within web.xml. No jndi-name attribute is required from jboss-web.xml. This behaviour has changed in Version 3.0.4. Deploying a Web Archive with a valid ejb-link attribute, but no jndi-name attribute, results in a Deployment Exception. Fuller details of the problem , and of tests carried out, are set out in a Word document within the attached zip file. JBoss Version 3.0.4 OS Windows XP Home JDK 1.4.0 -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 19:15 Message: 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. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 18:09 Message: 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. -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:02 Message: Logged In: YES user_id=665462 Document attached (hopefully) -- Comment By: James Strachan (strachancambs) Date: 2002-12-09 18:00 Message: Logged In: YES user_id=665462 Am sending the Word document separately - my attachment may have been too large for SourceForge to accept. -- Comment By: Christian Riege (lqd) Date: 2002-12-09 16:31 Message: 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=detailaid=629145group_id=22866atid=376685 for more information. have a fix for this in hand, just need to get around to add a testcase to the testsuite. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=650929group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
