This is correct.  JCS must be in the same level as your application.  If you
include your JCS libraries and your cached object classes at the server
classloader level, your webapps can share the same caches.  The big downside
of that is your war file now depends on third party libraries in the server
classpath.

Another way to get that same effect is to go with an EJB/Servlet container
and deploy an ear file with multiple wars.  This way your jcs libraries can
exist in the enterprise classloader and be shared by multiple web
applications.


----- Original Message -----
From: "Estefano Eduardo" <[EMAIL PROTECTED]>
To: "Turbine JCS Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, February 03, 2004 4:42 AM
Subject: RE: Configuration with multiple Tomcat webapps


I don't have experience with tomcat in particular, but I think they
should because the webapps are using different classloaders.

In any case, I think the jcs jar must be in the same classloader "level"
as your application, otherwise jcs will not be able to deserialize your
objects that are placed in disk cache.

Please anyone correct me if I'm wrong here.

-----Original Message-----
From: Russell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 03 February, 2004 7:15
To: Turbine JCS Users List
Subject: Configuration with multiple Tomcat webapps


I have several webapps running in one Tomcat instance. My concern is
with JCS keeping caches in the different webapps independent.

If I put a cache.ccf file in each webapp-specific WEB-INF/classes
directory and a copy of the JCS jar file in each webapp-specific
WEB-INF/lib directory, will the caches be separate for each webapp, even
though they use the same region names? [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to