• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Problem with wsimport based pulling from Websphere-7

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Think of how stupid the average person is. And how half of them are stupider than that. But who reads this tiny ad?
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic