Hi,
Consider the situation where two different services want to use two different 
versions of a third party library.If the two versions of the same 
jar(xyz-1.1.jar and xyz-1.2.jar) are put in the same location ,both the 
versions cannot be initialised in one JVM since the fully qualified names of 
the two classes are the same in both the versions. The only way to achieve this 
is to use seperate class loading mechanisms.If you want to use two versions of 
the same third party library then put them into service archive file so that 
the two services will be able to load without having any problems. 
 
 
 
 
Regards,
 
Yamini 
 

________________________________

From: falom [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 15, 2007 8:26 AM
To: [email protected]
Subject: [Axis2] purpose of using different classloaders


Hi,
 
This may be a basic thing to understand, but someone please help me to explain 
why Axis2 uses different classloaders for services under Tomcat or some other 
servlet containers. What is the major reason behind it.
 
falom

________________________________

抢注雅虎免费邮箱-3.5G容量,20M附件! <http://cn.mail.yahoo.com>
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

Reply via email to