my dog learned polymorphism*
The moose likes Web Services and the fly likes Problem with wsimport based pulling from Websphere-7 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Problem with wsimport based pulling from Websphere-7" Watch "Problem with wsimport based pulling from Websphere-7" New topic
Author

Problem with wsimport based pulling from Websphere-7

Ron Alby
Greenhorn

Joined: May 31, 2011
Posts: 24
I created the wsdl and build the web services. I have expectedContentTypes values in the wsdl to support MTOM. My Websphere generated client runs just fine, and does send the MTOM data in binary.

Here's the problem. When a client attempts to use wsimport to generate their client (hitting the http site), Websphere strips off the expectedContentTypes values and the client generates a non-MTOM client.


Here's the wsdl:



Here is what Webshphere returns for the wsdl:


And here is the referenced xsd (which Websphere stripped out of my wsdl all by themselves):


Note that all references to xmime:expectedContentTypes have been removed.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Problem with wsimport based pulling from Websphere-7