Updating mule classpath

6854933580_2c8b688306_z

This file contains settings for all the loaders other than the bootstrap loader, which is handled by the JVM, and the system loader, which is also handled by the JVM, after its values have been re-written by Tomcat's startup script.Examining this file, you'll notice a few things: The server loader should be left alone, but the shared loader still has many useful applications.

To understand how Tomcat resolves classpath, take a look at this outline of the Tomcat 6 startup process: There you have it.There are three answers to this question, and we'll tackle each of them in turn: Everything about Apache Tomcat aims to be as self-contained, intuitive, and automatic as possible, in an effort to standardize the configuration and deployment of web applications for efficient administration, while limiting access to different libraries for security and namespace reasons.This is why rather than using the Java "classpath" environment variable, which is the traditional place to declare dependency repositories, Tomcat's start scripts ignore this variable and generate their own classpaths when they create Tomcat's "system" classloader.This loader is also replaced with the Common loader.Additionally, Tomcat 5.x also included a Catalina loader, which loaded all Catalina components. If you are using Tomcat exactly as recommended by the documentation, you should not have any problems with classpath.There are some interesting naming conventions having to do with directory structure, but they've been around forever.

You must have an account to comment. Please register or login here!