Hi,
Yes allright sorry for my bad understanding of jndi, from Simone post on
what catalina is doing, it has more sense now.
Thanks.
> Not really because this potentially implies a new protocol. Who
> is generating
> the jndi://localhost:1099 url? Unless the JNDI spi spec indicates
> that jndi:
> should be treated specially by all JNDI providers, it doesn't make sense
> to arbitrarily add support for it.
>
> ----- Original Message -----
> From: "Vincent Harcq" <[EMAIL PROTECTED]>
> To: "Dev JBoss" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Friday, May 11, 2001 2:00 AM
> Subject: [JBoss-dev] RE: [JBoss-user] Catalina and Jboss2.2.1
> InitialContext error
>
>
> > 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
> >
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
