I think we're on the right track here. However, there are some things that I don't understand about your environment. Are you running the WTE that comes with WSAD or are you running a "remote" version of WebSphere in your server configuration? It looks from the boot.class.path (e:\WebSphere-Aes\AppServer ...) like you're running a remote version.
Do you have a copy of Xalan or Xerces in ibmfix.jar? What .jar files do you have in d:\WSAD\plugins\com.ibm.etools.server.jdk\jre\lib\ext? What visibility did you have set for this example? The bottom line is that I think you're picking up a version of XalanJ from somewhere other than your EAR. This loads only some of the XalanJ classes. Then, when you do your second call, for some reason it's picking up a class not loaded in the other version of XalanJ which is a subclass of a class that was previously loaded from your first XalanJ call. Since the base class and the subclass are in different classloaders, this causes the LinkageError. Are both calls in the same method? If not, where are the calls occurring and in what module? Is one in your WebApp and one in your EJB? When I get some answers to these questions, I think we'll be pretty close to diagnosing the problem. Gary > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 19, 2002 8:39 AM > To: [EMAIL PROTECTED] > Subject: RE: clues about classLoader problems > > > > > > For good measure, I have also added > System.err.print(tf.getClass ().getClassLoader().toString()); > and I now dump the exception directly, to give a cleaner > output (I guess I should have started doing all this ages > ago) > > This gives some interesting results (that I don't understand) : > <snip...>
