Thank you all. I went with Option 3 since the problem didn't seem to be
bubbling into our Dev environment and I am only seeing it on my local box.
For completness sake, I did notice that the line
d.setClassLoader(Thread.currentThread.getContex
tClassLoader())
should be
Try this:
Thread.currentThread().getContextClassLoader().loadClass(
mycompany.service.ups.dto.UPSResponseDTO )
Digester, by default, uses the thread context classloader. So, if it can't
find the class, then Digester can't instantiate it. You can optionally tell
Digester what classloader to use
That line of code appears to be working properly. I do not get a
ClassNotFoundException on the call to the below code. Any thoughts on why
this might be occurring? More information on my environment
IBM JDK 1.3 WebSphere 5.0
Thanks,
Michael
On 4/14/06, James Carman [EMAIL PROTECTED] wrote:
Hi Michael,
I think James is probably right.
By default, Digester will look for classes using the same Classloader
that loaded the Digester class. This means that if the
commons-digester.jar file is in some container-level dir (rather than in
WEB-INF/lib or similar) then it can't see that
