> From: David Delbecq [mailto:[EMAIL PROTECTED]
> Subject: Re: using JNDI to share object reference between two apps
>
> My experience have shown that, if you only use interfaces and the
> interfaces are in the same class loader, the actual classes
> do no matter.
Definitely
exprimait
en ces termes:
>> From: Angel Todorov [mailto:[EMAIL PROTECTED]
>> Subject: Re: using JNDI to share object reference between two apps
>>
>> Does tomcat perform explicit serialization of everything, even if JNDI
>> is used locally on the same JVM ?
>&g
En l'instant précis du 02/15/07 15:39, Caldarale, Charles R s'exprimait
en ces termes:
>> From: Angel Todorov [mailto:[EMAIL PROTECTED]
>> Subject: Re: using JNDI to share object reference between two apps
>>
>> Does tomcat perform explicit serialization of e
> From: Angel Todorov [mailto:[EMAIL PROTECTED]
> Subject: Re: using JNDI to share object reference between two apps
>
> Does tomcat perform explicit serialization of everything, even if JNDI
> is used locally on the same JVM ?
This has nothing to do with serialization; no s
Hi David,
Does tomcat perform explicit serialization of everything, even if JNDI
is used locally on the same JVM ? I wouldn't want to serialize
anything. Sure the producer (bind) and the consumer (lookup) will use
the same interface, but the producer doesn't have to care about the
classes used "b
En l'instant précis du 02/15/07 13:14, Angel Todorov s'exprimait en ces
termes:
> Hi all,
>
> I am new to tomcat's JNDI in general, and would like to achieve this
> very simple task: I have two webapps webapp1.war and webapp2.war. I
> would like to use a global JNDI context and bind an object refer
Hi all,
I am new to tomcat's JNDI in general, and would like to achieve this
very simple task: I have two webapps webapp1.war and webapp2.war. I
would like to use a global JNDI context and bind an object reference
from some servlet in webapp1 , and then look this up from some servlet
in webapp2.
