> > We want to host our new servlet product as an ASP. Each customer of
ours
> > would get a unique configuration for the product. However, all of the
> > servlets would run from one code base.
We tried to do the same thing, as that's rather the point of webapps. But
we ran into various problems, mostly related to classloader conflicts (3.2.1
and 3.2.2beta). We unfortunately could not resolve them (JNDI, JMS, JCE
libraries simply refused to work well, despite the fact that all of them
were stored in JAR files in the webapp's WEB-INF/lib directory). It seems
that somehow those types of services just don't share well in a single JVM,
or tomcat's classloaders were not working well enough to keep everything
segmented.
As it turned out for us, this is a problem from a load perspective, but it
does have some nice parts too. For example, if your 'customer2' becomes a
heavy user, you can more easily move the configuration from one server to
another. Also, it may become required that 'customer1' be put on a its own
server for business/political reasons.
Anyway, let me know if you can actually make it work when you use things
like JNDI, JMS, JCE or the like. It seemed like simple JSP-based webapps
that didn't do much would work, but when they made use of these pluggable
provider-based APIs, things got confused.
David
