I
don't agree that sharing classes doesn't pose many advantages as
compared to not sharing them - that's why there is the big topic named
"Jar Hell".
Regards,
Angel
On 2/20/07, Boris Unckel <[EMAIL PROTECTED]> wrote:
Hello,
Angel Todorov wrote:
> I have the foll
Hi All,
I have the following scenario: one webapp, which has some jars in its
private WEB-INF\lib dir, and one common jar which I would like to
share among several webapps. Hence, I am putting this jar into the
shared\lib directory of Tomcat. The problem is that this common lib
references classes
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
asses used "behind" that interface, since they are normally loaded
by the classloader of the producer (that does bind) web app. Is that
the case with tomcat? Thanks.
Best,
Angel
On 2/15/07, David Delbecq <[EMAIL PROTECTED]> wrote:
En l'instant précis du 02/15/07 13:14, Angel To
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.
