axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sedukhin, Igor" <Igor.Seduk...@ca.com>
Subject Axis and .NET inetrop failure due to WSDL4J!!
Date Sat, 02 Feb 2002 04:30:23 GMT
I was trying to consume some of the WSs exposed by latest Axis builds with an RTM VS.NET and
wasn't able to do it because of:
http://www.w3.org/2001/06/soap-encoding <http://www.w3.org/2001/06/soap-encoding> 
and
SOAP-ENC:string
These are the things generated by WSDL4J for the sake of supporting SOAP 1.2 encoding style.

I don't know what is the priority for other people using Axis, but I was relying on the interoperability
a lot. Is it so important for us to support SOAP 1.2, forgoing .NET RTM interop right now?

I think it should be selectable - a parameter on the service, to use SOAP 1.1 style of SOAP
1.2 style. I'm not sure if WSDL4J currently supports the selection? Does it? Anybody knows?

What was the latest WSDL4J that supported SOAP 1.1 encoding?

PS. WSDL4J still generates xsd:int anyways. What was the point of doing just SOAP-ENC:string
alone?

-- Igor Sedukhin .. (Igor.Sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788



Mime
View raw message