Nope.
Scott, my gentle jndi guru, does it make sense to change NamingContext
so that it can understand "jndi:", then use for java.naming.provider.url
something like "jndi://localhost:1099" to avoid this problem with catalina ?
Or is it Catalina the source of the problem ?
> > > > > > javax.naming.CommunicationException[Root exeption is
> > > > > > java.rmi.ServerException: RemoteException occured in server
> > > > > > thread; nested
> > > > > > exception is java.rmi.UnmarshalException: error unmarshalling
> > > > > > arguments;
> > > > > > nested exception is java.net.MalformedURL exception: unknown
> > > > > > protocol: jndi
Vincent
> Hi!
> You are the first one to get this :(
> I also got this one on beta3 but it works fine for me on beta1 :)
> beta4 is just out, I will try again...
> Vincent.
>
> >
> > Maybe the -nonaming is not getting executed then? (if it fixed your
> > problem). I am using Catalina from within the Turbine TDK which
> contains a
> > schell script startup.sh which calls the catalina.sh script. I
> have added
> > the -nonaming to this line so it reads
> >
> > $BASEDIR/catalina.sh start -nonaming "$@"
> >
> > This should turn naming off, but I still get the errors when I start the
> > program this way.
> >
> >
> > > Hey John
> > >
> > > > Yes, I have tried that, and I still get the error. (It seems
> > > > like it has no
> > > > effect) Do you have this configuration working?
> > >
> > > Not exactly. I'm using Catalina with another server application
> > > that has its
> > > own Naming service, and at the beginning I got the same error
> > on startup,
> > > but it went away with the -nonaming option.
> > > We then have other problems with this jndi: protocol, also
> from previous
> > > discussions it seems to me a Catalina bug: with us, every class
> > > loaded from
> > > web-inf/classes or web-inf/lib has a codebase like
> > > "jndi:/WEB-INF/classes/"
> > > or "jar:jndi:/WEB-INF/lib/xxx.jar!/", so that if objects of
> > these classes
> > > are passed as arguments to any rmi method invocation, on the
> > > other side the
> > > class annotation is taken from the stream, but of course the
> classloader
> > > cannot understand the Catalina-specific jndi: protocol.
> > > The context class loader should take care of that probably, but
> > I did not
> > > figured it out yet why it doesn't. I miss Rickard !
> > >
> > > Will live, will see.
> > >
> > > Cheers
> > >
> > > Simon
> > >
> > > > >
> > > > > Do you start Catalina with the -nonaming option, so that from it
> > > > > you connect
> > > > > to JBoss' Naming service ?
> > > > >
> > > > > Simon
> > > > >
> > > > > > -----Messaggio originale-----
> > > > > > Da: John Menke [mailto:[EMAIL PROTECTED]]
> > > > > > Inviato: mercoled� 9 maggio 2001 23:30
> > > > > > A: jboss
> > > > > > Oggetto: [JBoss-user] Catalina and Jboss2.2.1
> InitialContext error
> > > > > >
> > > > > >
> > > > > > This error is produced when I try to get an initial
> JNDI context.
> > > > > >
> > > > > > The error is:
> > > > > >
> > > > > > javax.naming.CommunicationException[Root exeption is
> > > > > > java.rmi.ServerException: RemoteException occured in server
> > > > > > thread; nested
> > > > > > exception is java.rmi.UnmarshalException: error unmarshalling
> > > > > > arguments;
> > > > > > nested exception is java.net.MalformedURL exception: unknown
> > > > > > protocol: jndi
> > > > > >
> > > > > >
> > > > > > I can get InitalContext in Tomcat 3.2, but Catalina produces
> > > > > > the error.
> > > > > >
> > > > > > Is there a workaround?
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
