A little background:
We are currently in the process of developing an
application that will be managed by Tomcat. We have several Java EE
applications that have been running with WebSphere for approximately 5 years.
Those applications include some classes that form a home grown application
framework that we wish to reuse as part of the new application targeted for
Tomcat.
The question/issue:
One of the classes that we would like to reuse resides
in a jar file that is contained at the shared jars folder within Tomcat and has
the capability using reflection to perform a “factory” behavior and
instantiate various classes based on their fully qualified name.
When this “factory” needs to instantiate a
class that resides in the shared jars folder it works great. However, when the
class to be instantiated resides below that, i.e. an application it is subject
to the rules of delegation in the classloader hierarchy, and fails trying to
instantiate the class.
As mentioned above, we have used this class for
several years in WAS. In that case, the jar that contains the factory resides
at the EAR level and can instantiate classes that live in the associated WAR
files just fine. The problem only exists in Tomcat.
Admittedly, we are new to using Tomcat and are looking
to see if there is a way where we might configure Tomcat’s behavior to
mimic that of an app. server like WebSphere?
Francis A. Varin,
M.S.
IT
Architect II
Corporate
Information Systems
Amica Mutual
Insurance Company
1-800-652-6422
ext. 24536
http://www.amica.com
**********************************************************
This email and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you have received this email in error please notify
[EMAIL PROTECTED]
and the sender of the message. Thank you.
**********************************************************