It was a classpath issue. I wasn't aware of the fact that you can change
the classpath setting of WebSphere 6.1 in two places. Obviously, I
changed it at the wrong place. In case you have a similar issue, try to
change the classpath setting as follows:
Got to Applications/Enterprise Applicatio
Make sure that you have the appropriate wsdl4j jar on your application's
classpath. If you do, you will probably need to do more research to see where
the conflicting jar is coming from. I think WebSphere provides the ability to
dump the classloader but I can't remember how to do it.
Below is
