Loading ...
Sorry, an error occurred while loading the content.

10053RE: [soapbuilders] .NET, SOAP encoded types and arrays

Expand Messages
  • Kirill Gavrylyuk
    Dec 17, 2004
    • 0 Attachment
      Hi Eric,
      you mean rpc/literal?
      Our current plan is to support rpc/literal in .Net 2.0 - it's available
      in 2.0 Beta1 released this summer.

      >-----Original Message-----
      >From: Eric Rajkovic [mailto:eric.rajkovic@...]
      >Sent: Friday, December 17, 2004 12:07 PM
      >To: soapbuilders@yahoogroups.com
      >Subject: RE: [soapbuilders] .NET, SOAP encoded types and arrays
      >
      >
      >Hi Kirill,
      >
      >I could not resist but ask the other question
      >
      >any plans to support literal, other than by pointing at r2d on
      gotdotnet ?
      >
      >Eric
      >
      >-----Original Message-----
      >From: Kirill Gavrylyuk [mailto:kirillg@...]
      >Sent: Friday, December 17, 2004 11:48 AM
      >To: soapbuilders@yahoogroups.com
      >Subject: RE: [soapbuilders] .NET, SOAP encoded types and arrays
      >
      >
      >Hi Tom,
      >Does your WSDL contain xsd:import for soap-encoding schema?
      >
      >While we're on the topic, any plans to change your default from encoded
      to
      >literal?
      >
      >Thanks
      >
      >>-----Original Message-----
      >>From: Tom Jordahl [mailto:tomj@...]
      >>Sent: Friday, December 17, 2004 11:13 AM
      >>To: 'soapbuilders@yahoogroups.com'
      >>Subject: RE: [soapbuilders] .NET, SOAP encoded types and arrays
      >>
      >>
      >>
      >>Well, that is cool for document/literal web services, but there are
      >still
      >>*many* toolkits (like say, Axis) that default to rpc/encoded.
      >>
      >>WS-I says nothing about encoding behaviors (other than not to use
      >them).
      >>So
      >>it doesn't apply here. This is a .NET failure to consume what I think
      >is a
      >>legitimate rpc/encoded web service.
      >>
      >>But thanks for playing Chris! :-)
      >>
      >>--
      >>Tom Jordahl
      >>Macromedia Server Development
      >>
      >>> -----Original Message-----
      >>> From: Christopher B Ferris [mailto:chrisfer@...]
      >>> Sent: Friday, December 17, 2004 1:50 PM
      >>> To: soapbuilders@yahoogroups.com
      >>> Subject: Re: [soapbuilders] .NET, SOAP encoded types and arrays
      >>>
      >>>
      >>> Could be because WS-I BP1.x disallows use of SOAP encoding. It has
      >always
      >>> been my understanding
      >>> that .NET would not support SOAP encoding.
      >>>
      >>> Bottom line, you want interop, color inside the lines drawn by the
      >WS-I
      >>> Profiles:-)
      >>>
      >>> Cheers,
      >>>
      >>> Christopher Ferris
      >>> STSM, Emerging e-business Industry Architecture
      >>> email: chrisfer@...
      >>> blog: http://webpages.charter.net/chrisfer/blog.html
      >>> phone: +1 508 377 9295
      >>>
      >>> Tom Jordahl <tomj@...> wrote on 12/17/2004 12:20:40 PM:
      >>>
      >>> > Hello,
      >>> >
      >>> > Axis recently fixed up its type mapping system and our users have
      >>> reported
      >>> > some interop problems. Specifically, .NET client does not seem to
      >>> > understand the soapenc types that Axis is sending it in SOAP
      >encoded
      >>> arrays.
      >>> >
      >>> > Our WSDL is this:
      >>> >
      >>> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
      >>> >
      >>> > <complexType name="ArrayOf_soapenc_string">
      >>> > <complexContent>
      >>> > <restriction base="soapenc:Array">
      >>> > <attribute ref="soapenc:arrayType"
      >>> wsdl:arrayType="soapenc:string[]"/>
      >>> > </restriction>
      >>> > </complexContent>
      >>> > </complexType>
      >>> >
      >>> > For an operation that is simply:
      >>> > String[] echo(String[] in)
      >>> >
      >>> > .NET client sends this (note that it doesn't use the soap encoded
      >>> types):
      >>> >
      >>> > <soap:Body
      >>> soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
      >>> > <q1:echo xmlns:q1="http://DefaultNamespace">
      >>> > <in href="#id1" />
      >>> > </q1:echo>
      >>> > <soapenc:Array id="id1" soapenc:arrayType="xsd:string[3]">
      >>> > <Item>one</Item>
      >>> > <Item>two</Item>
      >>> > <Item>three</Item>
      >>> > </soapenc:Array>
      >>> > </soap:Body>
      >>> >
      >>> >
      >>> > Axis 1.2 returns:
      >>> >
      >>> > <soapenv:Body>
      >>> > <ns1:echoResponse
      >>> >
      soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/
      >>> > xmlns:ns1="http://DefaultNamespace">
      >>> > <echoReturn soapenc:arrayType="soapenc:string[3]"
      >>> > xsi:type="soapenc:Array"
      >>> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
      >>> > <item>one</item>
      >>> > <item>two</item>
      >>> > <item>three</item>
      >>> > </echoReturn>
      >>> > </ns1:echoResponse>
      >>> > </soapenv:Body>
      >>> >
      >>> >
      >>> > .NET reports an error:
      >>> > Unhandled Exception: System.InvalidOperationException: There is an
      >>error
      >>> in
      >>> > XML document (1, 308). ---> System.InvalidOperationException: The
      >>> specified
      >>> > type was not recognized: name='string',
      >>> > namespace='http://schemas.xmlsoap.org/soap/encoding/', at
      ><whoamiReturn
      >>> > xmlns=''>.
      >>> >
      >>> > Actually, C# only says "There is an error in XML document (1,
      >311)." -
      >>> this
      >>> > error is from our user who is using VB.
      >>> >
      >>> > It appears that only by accident did our previous releases not use
      >the
      >>> SOAP
      >>> > encoded types due to bugs in our code. Now that we fixed them,
      >this
      >>> shows
      >>> > up. :-}
      >>> >
      >>> > Why is .NET not using the soapenc types? Why is it unable to
      >recognize
      >>> > these types in a rpc/encoded service? What are other
      >implementation
      >>> doing
      >>> > (particularly JAX-RPC implementation) about the SOAP encoded
      types?
      >>> >
      >>> > Thanks for any help/info.
      >>> >
      >>> > --
      >>> > Tom Jordahl
      >>> > Wearing his Apache Axis committer hat
      >>> >
      >>> >
      >>> >
      >>> >
      >>> > -----------------------------------------------------------------
      >>> > This group is a forum for builders of SOAP implementations to
      >discuss
      >>> implementation and
      >>> > interoperability issues. Please stay on-topic.
      >>> >
      >>>
      >>> >
      >>> > Yahoo! Groups Sponsor
      >>> >
      >>> > ADVERTISEMENT
      >>> > [image removed]
      >>> >
      >>> > [image removed]
      >>> >
      >>> >
      >>> > Yahoo! Groups Links
      >>> > To visit your group on the web, go to:
      >>> > http://groups.yahoo.com/group/soapbuilders/
      >>> >
      >>> > To unsubscribe from this group, send an email to:
      >>> > soapbuilders-unsubscribe@yahoogroups.com
      >>> >
      >>> > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
      >Service.
      >>>
      >>>
      >>>
      >>> -----------------------------------------------------------------
      >>> This group is a forum for builders of SOAP implementations to
      discuss
      >>> implementation and interoperability issues. Please stay on-topic.
      >>> Yahoo! Groups Links
      >>>
      >>>
      >>>
      >>>
      >>>
      >>
      >>
      >>
      >>
      >>-----------------------------------------------------------------
      >>This group is a forum for builders of SOAP implementations to discuss
      >>implementation and interoperability issues. Please stay on-topic.
      >>Yahoo! Groups Links
      >>
      >>
      >>
      >>
      >>
      >>
      >
      >
      >
      >
      >-----------------------------------------------------------------
      >This group is a forum for builders of SOAP implementations to discuss
      >implementation and interoperability issues. Please stay on-topic.
      >Yahoo! Groups Links
      >
      >
      >
      >
      >
      >
      >
      >
      >
      >
      >
      >-----------------------------------------------------------------
      >This group is a forum for builders of SOAP implementations to discuss
      >implementation and interoperability issues. Please stay on-topic.
      >Yahoo! Groups Links
      >
      >
      >
      >
      >
      >
    • Show all 17 messages in this topic