I was not able to bind a client to a service. Proxy generator complained about unknown encoding used in the description.
It actually looks like it was/is Axis problem and not WSDL4J at all. (My fault :). I have started moving up the nigthly builds befrore I hit this problem. I could not go beyond Jan 26 because of deployment changes :). It'll take a while. Anyway, it was fixed on Jan 28, but I still have to get to it. False alarm, sorry. -- Igor Sedukhin .. ([EMAIL PROTECTED]) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 02, 2002 9:05 AM To: [EMAIL PROTECTED] Subject: Re: Axis and .NET inetrop failure due to WSDL4J!! AXIS, by default, is supposed to be SOAP 1.1. We don't yet have a switch for SOAP 1.2, but we're thinking about it. Some of our WSDL2Java tests are testing SOAP 1.2 types (soap-enc:xxx) because mappings for them are defined in JAX-RPC, but I think AXIS still sends SOAP 1.1 over the wire. Perhaps we missed something. Could you tell us exactly what you couldn't do? Russell Butek [EMAIL PROTECTED] "Sedukhin, Igor" <[EMAIL PROTECTED]> on 02/01/2002 10:30:23 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Axis and .NET inetrop failure due to WSDL4J!! 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 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 .. ([EMAIL PROTECTED]) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
