Re: Tomcat 5.5.9, endorsed jars and classloader

2005-09-01 Thread Antti Rauramo

Yoav Shapira wrote:

With older tomcats this has been works fine for years now, but with 
5.5.9 an IllegalAccessException is thrown.
   



Which older Tomcats?  Specifically, does it work in 5.0.28 or 5.5.7?  4.x and
5.x tell a bit of a different story when it comes to classloading
implementation.
 


The older is 4.1.31.

The server with Tomcat 4.1.31 runs Sun's JDK 1.5.0-b64, the one with 
Tomcat 5.5.9 runs Sun's JDK 1.5.0_04-b05. It is possible for me to 
upgrade the other if you think this may be an issue. The classloaders 
toString() output is actually different, come to think of it...
   



It would be good to make them use the same JVM version, if only to rule out
that variable.  But better yet, please test 5.0.28 and 5.5.7.
 


Tomcat 5.0.16 and Sun's JDK 1.4.2_02: valid classloader for A, null for B.

Sorry, for now I try to use the Tomcat's that I already have 
installed... But this seems to rule out the JVM version, and pinpoint 
the change to have happened between 4.x and 5.0.x.



--
Antti Rauramo
Index Information Technologies Oy
[EMAIL PROTECTED]
+358-40-5190209 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5.9, endorsed jars and classloader

2005-08-31 Thread Antti Rauramo

Hello all,

I ran into problems with Tomcat 5.5.9. We have xercesImpl.jar in 
common/endorsed, and another jar (X-Hive's XML database's xhive.jar) in 
common/lib, that includes a class that is put in the xerces package 
(org.apache.xerces.dom) in order to access xerceses package protected 
class ObjectFactory. This works as long as the classloader is the same 
for both xerces and xhive.


With older tomcats this has been works fine for years now, but with 
5.5.9 an IllegalAccessException is thrown.


I wrote a test case that seems to prove the case, or at least some 
difference. Basically there are two classes, testing.A and testing.B. A 
creates an instance of B and accesses a method that returns the 
instances classloader.


When A is in common/lib/a.jar and B in common/lib/b.jar, both Tomcats 
displays the same classloaders for A and B.


When A is in common/lib/a.jar and B in common/endorsed/b.jar, Tomcat 
4.1.31 displays the same classloaders for both A and B, but Tomcat 5.5.9 
displays a classloader for A but null for B.


The server with Tomcat 4.1.31 runs Sun's JDK 1.5.0-b64, the one with 
Tomcat 5.5.9 runs Sun's JDK 1.5.0_04-b05. It is possible for me to 
upgrade the other if you think this may be an issue. The classloaders 
toString() output is actually different, come to think of it...


The test files are at 
http://www.index.fi/indox/download/tomcat-classloader-test.tar so you 
can easily see for yourselves.


--
Antti Rauramo
Index Information Technologies Oy
[EMAIL PROTECTED]
+358-40-5190209 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5.9, endorsed jars and classloader

2005-08-31 Thread Yoav Shapira
Hi,

 I ran into problems with Tomcat 5.5.9. We have xercesImpl.jar in 
 common/endorsed, and another jar (X-Hive's XML database's xhive.jar) in 
 common/lib, that includes a class that is put in the xerces package 
 (org.apache.xerces.dom) in order to access xerceses package protected 
 class ObjectFactory. This works as long as the classloader is the same 
 for both xerces and xhive.

It's still a hack ;)  But I've done it myself in the past...

 With older tomcats this has been works fine for years now, but with 
 5.5.9 an IllegalAccessException is thrown.

Which older Tomcats?  Specifically, does it work in 5.0.28 or 5.5.7?  4.x and
5.x tell a bit of a different story when it comes to classloading
implementation.

 The server with Tomcat 4.1.31 runs Sun's JDK 1.5.0-b64, the one with 
 Tomcat 5.5.9 runs Sun's JDK 1.5.0_04-b05. It is possible for me to 
 upgrade the other if you think this may be an issue. The classloaders 
 toString() output is actually different, come to think of it...

It would be good to make them use the same JVM version, if only to rule out
that variable.  But better yet, please test 5.0.28 and 5.5.7.

Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]