Return-Path: 
 <tomcat-dev-return-18798-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 31025 invoked by uid 500); 14 Mar 2001 17:25:29 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:tomcat-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:tomcat-dev@jakarta.apache.org>
Reply-To: tomcat-dev@jakarta.apache.org
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 30982 invoked from network); 14 Mar 2001 17:25:26 -0000
Message-ID: <20010314170652.15053.qmail@pop3.ticnet.com>
References: <20010313231541.13475.qmail@pop3.ticnet.com>
            <01a401c0ac18$49202590$82deb018@intalio.com>
            <000401c0ac3a$13199c20$22f6493f@home>
            <02d801c0ac46$c4edf070$82deb018@intalio.com>
In-Reply-To: <02d801c0ac46$c4edf070$82deb018@intalio.com>
From: tttye@ticnet.com
To: tomcat-dev@jakarta.apache.org
Subject: Re: Strange problem with URL_PKG_PREFIXES
Date: Wed, 14 Mar 2001 17:06:52 GMT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N


Remy,
Thanks for helping me look into this problem.  
I believe that short term, prepending the apache pkg prefix is a simple way
to make results consistent.  
I thought that some of my problem might be from having out of date
'org.jnp.interface' library.  I have looked all morning, and cannot find
anything outside of JBoss that includes this jar, so I have no explaination
why Jakarta is able to get a naming context from JBoss instead of Class
load fail!!!  How do I find out where a servlet class loader is obtaining a
class from (which jar path)? 

I am trying to make the <ejb-link> use jnp://ttt1:1099/EJBresource work.  
I need to resolve this type of URL link in Jakarta to allow seperation
between the JSP server and the EJB server.
The org.apache.naming.NamingContext does not seem to pass the correct
information to NamingManager so it can connect to the jnpURLNaming....
Can you think of anything else to try?


Remy Maucherat writes:

> > According to NamingManager documentation, first it will look for
> > 'org.jnp.interfaces.java.javaURLContextFactory' which does not exist, so
> it
> > should next look for 'org.apache.naming.java.javaURLContextFactory' which
> > does exist.
> > So, this should work.
> 
> Indeed, my mistake. It should work, since the IC will only call lookup on
> the Context produced by the IC factory *after* checking the URLs.
> 
> > BTW, the 'org.apache.naming' prefix is concatenated onto the URL prefixes
> by
> > jakarta.
> 
> Since I can't figure out where the problem is coming from, I can change it
> and make 'org.apache.naming' a prefix.
> 
> > Also, when the jnp.jar is removed, it still fails with the same
> > error.
> > How can this be made to work?
> 
> Don't you get a no initial context factory found when you remove JNP ?
> 
> Remy
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, email: tomcat-dev-help@jakarta.apache.org