Bugs item #581847, was opened at 2002-07-15 21:42
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=581847&group_id=22866
Category: JBossSOAP
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Mario Däpp (mdaepp)
Assigned to: Dr. Christoph Georg Jung (cgjung)
Summary: <ejb-link> doesn't work properly
Initial Comment:
System Info:
21:12:20,813 INFO [Server] JBoss Release: JBoss-3.0.0
CVSTag=JBoss_3_0_0
21:12:29,812 INFO [ServerInfo] Java version: 1.4.0,Sun
Microsystems Inc.
21:12:29,813 INFO [ServerInfo] Java VM: Java
HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc.
21:12:29,814 INFO [ServerInfo] OS-System: SunOS 5.8,sparc
This is JBoss with Tomcat.
I'm using a slightly altered version of the original
jboss-net.sar (replaced AxisService to fix the /axis/*
context root problem with Catalina)
<ejb-link> in <ejb-ref> in web-service.xml doesn't work
propertly. If I enter the <bean-name> here (that's what
I think belongs here), then it doesn't work
(NamingException on the client side saying that
UppercaseService is not bound). If I enter the JNDI
name, it works.
I expect this bug to be reproducible if the JNDI name
in jboss.net.sample.hello.ejb.HelloBean is changed to
something else than Hello.
Excerpt from web-service.xml:
...
<ejb-ref>
<ejb-ref-name>ejb/UppercaseService</ejb-ref-name>
<!-- <ejb-link>UppercaseService</ejb-link> *DOESN'T
WORK* -->
<ejb-link>local/oois/demo/UppercaseService</ejb-link>
</ejb-ref>
<service name="Uppercase" provider="Handler">
<parameter name="handlerClass"
value="org.jboss.net.axis.server.EJBProvider"
/>
<parameter name="beanJndiName"
value="java:comp/env/ejb/UppercaseService" />
<parameter name="homeInterfaceName"
value="ch.isbiel.oois.demo.UppercaseServ
iceLocalHome" />
...
Excerpt from UppercaseServiceBean:
/**
* @ejb:bean name="UppercaseService" type="Stateless"
display-name="UppercaseServiceEJB" view-type="local"
local-jndi-name="local/oois/demo/UppercaseService"
* @ejb:interface generate="local"
* @ejb:util generate="logical"
*/
public class UppercaseServiceBean implements SessionBean {
...
----------------------------------------------------------------------
>Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2002-09-06 18:41
Message:
Logged In: YES
user_id=175199
feature is now marked deprecated and will vanish with next
release.
----------------------------------------------------------------------
Comment By: Mario Däpp (mdaepp)
Date: 2002-07-17 13:21
Message:
Logged In: YES
user_id=136508
Hi Christoph,
basically, you're right. However, I like the idea of
<ejb-refs> in web-service.xml. If I was able to specify
<ejb-name> in <ejb-link>, then there would be no dependency
between jboss.xml and web-service.xml in terms of the JNDI
name (and one file change down when somebody needs to change
the JNDI name for some reason ;-)). Don't know whether that
argument is strong enough though...
I'll check whether the same bug is present for <ejb-link> in
web.xml as well, because AFAIK the semantics should be no
different from ejb-jar.xml.
Mario
----------------------------------------------------------------------
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2002-07-17 12:23
Message:
Logged In: YES
user_id=175199
Hi,
I have to admit that I "implemented" the <ejb-ref/> feature in
the web-service.xml by simple copying&pasting from the
WebContainer code.
Hence it follows the same semantics than <ejb-ref/> in web-
application.xml (which could be different from <ejb-ref/> in ejb-
jar.xml, me totally ignorant here????)
In the meantime, I have come to the conclusion that the
feature doesn´t buy you anything in your web-service
implementation.
Unlike in a web-app: In your web-app, you will implement a
servlet, hence java code, that runs against the link names
instead of the mapped and changeable jndi names, right?
In your web-service there is no additional Java code involved
that hardcodes the JNDIname. Hence I would suggest that
you use the fully-qualified jndiname to your bean directly in
the EJBProvider service definition and leave the ejb-refs out. It
doesnt matter if you have to change the ejb-ref or the
jndiName entry in the web-service.xml, right?
So <ejb-ref/> will vanish in one of the next versions of
jboss.net, unless you have another strong argument for it
(security? I really dunno).
CGJ
----------------------------------------------------------------------
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2002-07-17 12:22
Message:
Logged In: YES
user_id=175199
Hi,
I have to admit that I "implemented" the <ejb-ref/> feature in
the web-service.xml by simple copying&pasting from the
WebContainer code.
Hence it follows the same semantics than <ejb-ref/> in web-
application.xml (which could be different from <ejb-ref/> in ejb-
jar.xml, me totally ignorant here????)
In the meantime, I have come to the conclusion that the
feature doesn´t buy you anything in your web-service
implementation.
Unlike in a web-app: In your web-app, you will implement a
servlet, hence java code, that runs against the link names
instead of the mapped and changeable jndi names, right?
In your web-service there is no additional Java code involved
that hardcodes the JNDIname. Hence I would suggest that
you use the fully-qualified jndiname to your bean directly in
the EJBProvider service definition and leave the ejb-refs out. It
doesnt matter if you have to change the ejb-ref or the
jndiName entry in the web-service.xml, right?
So <ejb-ref/> will vanish in one of the next versions of
jboss.net, unless you have another strong argument for it
(security? I really dunno).
CGJ
----------------------------------------------------------------------
Comment By: Mario Däpp (mdaepp)
Date: 2002-07-17 12:00
Message:
Logged In: YES
user_id=136508
Sorry, there's a typo. What I meant to write was <ejb-name>
istead of <bean-name>.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=581847&group_id=22866
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
