<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 14.07.2011 19:43, Michael Anstis wrote:
<blockquote
cite="mid:CAAG9P0sZ2Tm36Z-2FTivqS-3T=67A_UN0AroVrwo4khCVZZvwA@mail.gmail.com"
type="cite">IIRC, WAS's classloaders work in a different order to
other containers.<br>
<br>
I might be talking a load of baloney<span id="hotword"><span
style="cursor: default; background-color: transparent;"
id="hotword" name="hotword"></span></span> but I have a
feeling this is the case.<br>
<br>
I have another feeling you can configure this to be top-down or
bottom-up or something along those lines. Might be worth a try.<br>
<br>
If this is all found to be complete rubbish I'll visit my doctor
about these feelings I keep getting ;)<br>
</blockquote>
Definitely true, WAS classloaders can be ... interesting .... at
times :-)<br>
<br>
Copying JARs into the WAS library folder often does more harm than
it helps. I'd try the following:<br>
- remove all JARs you copied into WAS lib folder<br>
- deploy the WARs again and make sure you select the "PARENT LAST"
classloader option during deployment<br>
- if you're still getting class not founds, post the classname (and
specify the WAS version you're using) and I'll see if I can help<br>
<pre class="moz-signature" cols="72">--
CU, Joe</pre>
</body>
</html>