Rainer Jung escribío: > The catalina.properties file is the one that defines the classloader > search order. So you are free to make the order fit your own needs. > > For instance if you really like to share product installations and want > to add instance specific things to the common loader, you would add a > folder of your choice or a "*.jar" pattern inside CATALINA_BASE to the > common.loader in catalina.properties. > > If there is a conflict between the home and the base classes, the order > in the common.loader string will decide which gets loaded (first comes > first). > > By the way: all class loaders used in former Tomcat releases are still > present in TC 6 and there functionality is the same. Because this class > loader hierarchy confused a lot of users, we decided to switch to a > simple default distribution layout by moving everything into the common > classloader. In catalina.properties you can see, that all loaders > (common, server, shared) are still there and configurable, but only > common has classes in its search path.
Thanks. I saw that in catalina.properties. If I fill those values in (for the appropriate classloader) I can duplicate the behavior of the older systems. That will help in migrating large installations that are running tomcat 5 to tomcat 6. Is there a need to move to the "newer" common classloader? I guess my question is if the older ways will be deprecated in the future? Thanks. -- Brian Millett - [ N'Grath and Garibaldi, "Survivors"] "You are police." 'Not any more. I'm a fugitive. Don't tell me you haven't heard?' "Have heard. You are *still* police." --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
