Hi Chris,
Thanks for prompt response. We have like maybe 50 webapps, and they are
common (except that they have different database connection or maybe some
html file changes). Which is why we prefer sharing libraries for ease of
deployment and updates.
But I do agree, sharing libraries have their own shortcomings. Just
wondering if there are any workarounds at the moment for shared jar files.
Thanks.
Regards,
Kok Hoor
On Tue, Dec 28, 2021 at 8:05 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Kok Hoor,
>
> On 12/27/21 18:36, Chew Kok Hoor wrote:
> > Hi,
> >
> > We're using the old javax.servlet namespace for compatibility
> reasons.
> >
> > Some of our jar files are re-used by different web-apps, therefore
> we
> > placed them in the common classloader.
> >
> > Is it possible to convert them dynamically, just like how we do it
> for
> > servlets in the per app WEB-INF folder, by using the following in the
> > context file:
> >
> > <Loader jakartaConverter="TOMCAT" />
>
> Any reason not to simply *stop* using the shared ClassLoader and instead
> bundle everything with each web application?
>
> How many web apps are running in the same container? How many libraries
> are you sharing?
>
> I've never seen a good argument for sharing libraries like this. RAM is
> cheap and plentiful, and code is very small.
>
> -chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
