File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes Can't create the right SOAPFactory when running in WebSphere. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Can Watch "Can New topic

Can't create the right SOAPFactory when running in WebSphere.

Jesse Liberty

Joined: Jul 22, 2009
Posts: 1
We have some JAX-WS web service code that runs within WebSphere 6.1. We call a third-party Java library (IBM FileNet P8) that interacts with some other web services on another server.

Running our code from the command line works just fine. However, when we deploy to WebSphere, somewhere within these third-party libraries, the following fatal exception is thrown:

I dug into some of those methods and found that there is a call SOAPFactory.newInstance() that returns a type of: This class seems to cause the incompatibility.

In GlassFish, I can get the same code working by setting the property javax.xml.soap.SOAPFactory=com.systinet.saaj.soap.SOAPFactoryImpl. According to this javadoc article that changes the SOAPFactory that gets used. When I do this in GlassFish, the code works.

The problem is that this property doesn't seem make any difference within WebSphere.

Any ideas about how I could do more to either diagnose or fix this problem? Thanks!
Michael Heinrich

Joined: Feb 26, 2010
Posts: 1
Did you find a solution for your problem. I'm facing the same problem an could find a solution.
Praveen Kumar Jayaram
Ranch Hand

Joined: Jul 14, 2008
Posts: 56
Got any solution?

I agree. Here's the link:
subject: Can't create the right SOAPFactory when running in WebSphere.
It's not a secret anymore!