Thank you for replying.
> - is your production environment is using mixture of application servers
> that need to share the same data?
Not at the moment, but I would like to start testing Jetty instead of
Tomcat. And having terracotta block this experimentation, and not allow
me to do a gradual switch over, testing at every step.. not good at all.
> - do you have requirement to share the same data between different web
> applications?
Yes.
> For the second scenario, assuming that there is a common jar contain
> classes used for that shared data, the work around is to put that jar
> into a shared or common class loader or Tomcat (i.e. deploy it outside
> of your web applications, which would give additional memory benefits if
> more then one web application on the same server is using those
> classes). Those classloaders will have the same names across Terracotta
> clister, when all clustered web apps are running on Tomcat. See [1] for
> more details about Tomcat classloaders.
OK. Now I understand what you guys were talking about. We do not have
more than one app per server, but we do have many different web apps.
And this is still a major pain because it would totally screw with a
clean war file deploy wouldn't it? You would then have to figure out
where the shared classes are and make sure that they aren't using any
static variable, and lots of testing.. etc etc etc... I would love to
avoid that if possible. Since packaging up a webapp would require many
extra steps to break it up into the app specific and the
sharable/distributes parts...
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users
