my dog learned polymorphism*
The moose likes Web Services and the fly likes .Net Interoperablity issue with Xfire generated Webserivces Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark ".Net Interoperablity issue with Xfire generated Webserivces" Watch ".Net Interoperablity issue with Xfire generated Webserivces" New topic
Author

.Net Interoperablity issue with Xfire generated Webserivces

Venkat Srinivas
Greenhorn

Joined: Aug 02, 2006
Posts: 5
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
Venkat
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: .Net Interoperablity issue with Xfire generated Webserivces
 
Similar Threads
Why do I see different wsdl and xsd generated for webservice through wsgen.
Axis2 parameter ordering is wrong when not all elements are not passed
access to .net web service
passing primitive data types via webservices using WSAD and VisualStudion .NET
JBoss WSDL - custom schema types issues