• 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 ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Mike London

.Net Interoperablity issue with Xfire generated Webserivces

Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have Xfire generated Webservice WSDL, and a .Net client has to talk with this service.

My constraint here is .Net client has already got a client proxy generated for a webservice hosted by .Net and the same proxy class (as both Xfire Webservice and .Net webservice host the same API's)
will used be for Xfire webservice also without any change except the WSDL URL.

But this is not working as my XFire WSDL is having SOAPResponse 'minOccurs' element for a particular API as '1' where as proxy generated is not supporting this because it was generated for .Net WSDL which has SOAPResponse 'minOccurs' element for the same API as '0'.

Also the other difference is .Net generated WSDL is of version SOAP1.1, Where as Xfire generated WSDL is of version SOAP1.2 ...is the issue due to this version difference..?

Can anyone suggest me a way to make minOccurs as '0' for the 'SOAPResponse' element in Xfire generated webservices..?

Thanks in advance
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic