True, there is an <env-entry> tag in web.xml which should bind a name to a
value for "/ejb/catalog/CatalogDAOClass" which should in turn, I assume, be
accessible from the servlet using
"java:comp/env/ejb/catalog/CatalogDAOClass".
I don't think, however, that JBoss 2.2.2 binds <env-entry>s from web.xml
into the jndi tree under a tomcat scope. You have to use jboss-web.xml.
Buuuuutttt, that gets into something circular: you can't reference something
from jboss-web.xml unless it has already been bound into the jndi directory
and as a result you can't add environment variables to the jndi directory
for the tomcat scope using either the web.xml or jboss-web.xml files. You
have to do it progammatically, as far as I can tell.
If somebody could enlighten me by either confirming or explaining what
really goes on I would be very greatful.
j.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of danch (Dan
Christopherson)
Sent: Friday, June 29, 2001 2:09 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Possible naming bug JBoss 2.2.2 with Tomcat
3.2.2
J. King wrote:
>
>
> The puzzling question remains, how is it that this works on J2EE RI and
not
> JBoss? Moreover, how would I make this variable available in JNDI to both
> callers?
>
> j.
There should be a resource ref for it in the web.xml descriptor for the
war file. That's how you map into the ENC for web components. You'd also
need to do mapping in jboss-web.xml (I believe that's the correct name)
-danch
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
