Quoting [EMAIL PROTECTED]:
> 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'll put that in this evening.
> 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)?
You don't :-(
We just register the class repositories in a URLClassLoader, and let it do its
magic.
> I am trying to make the <ejb-link> use jnp://ttt1:1099/EJBresource work.
So it doesn't work either the other way around ?
> 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?
If you call (new InitialContext()).lookup("jnp://ttt1:1099/EJBresource"), then
it's supposed to work if the jnp URL context factory is in the classpath.
Nothing special has to be done in NamingContext (the same is true for the java
URLs and JNP - that's why I can't figure out why it doesn't work).
The com.sun.naming.internal.ResourceManager.getFactory method which is
ultimately called to return the appropriate URL context factory seems to be
doing what's expected.
Of course, the usual suspect when something really strange happens in Catalina
is the classloader, so it may be the root cause of this.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
