Reply-to-my question:
On Mon, Nov 3, 2014 at 6:42 PM, Neven Cvetkovic <neven.cvetko...@gmail.com>
wrote:
>
> SLIGHTLY-OFFTOPIC:
>
> Although, I would love to see out-of-box setup for additional shared-lib
> folder, something other than TOMCAT/lib with Tomcat default libraries.
> Essentially, I would love to separate my customer shared libraries from
> Tomcat default libraries. I guess - question would be where are
> CATALINA_HOME/lib JAR files being loaded from? Can we add another directory
> to scan for libraries to be loaded? Is that configurable?
>
>
>
I guess, it's easy to add new directories to
TOMCAT/conf/catalina.properties file:
common.loader=
${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar
to now read:
common.loader=
${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.base}/shared,${catalina.base}/shared/*.jar,${catalina.home}/shared,${catalina.home}/shared/*.jar
What are you thoughts? Would it make sense to keep a separate directory for
shared libraries? Should we make it default - to encourage others to create
a directory if they want to. Default behaviour for
org.apache.catalina.startup.ClassLoaderFactory is to validate if the file
exists/isDirectory/isReadable? That might confuse beginners with a Warning
...
I guess Tomcat philosophy is to keep it simple, and extensible - so experts
that need to customize things they can, and it is simple and not confusing
for beginners.
What are your thoughts?
Cheers!
Neven
