xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven J. McDowall" <sjmcdow...@uswest.net>
Subject RE: xml-soap and xsi:type requirements
Date Fri, 11 Aug 2000 13:16:28 GMT
RE: [SOAP] SOAP spec 1.1 and SOAP/Perl 0.23?
The reason why it requires it is because the SOAP spec 1.1. specifically
states that all
parameters must either have a "type" attribute or otherwise must inherently
be known
(either via something like a Schema or SCL, etc.). Since Schemas aren't well
supported
(or even passed yet), and SCL is still too new (or even NSSL) the decision
was made
(I can only imagine) to follow the spec by doing type= ..

Keith, for my Perl hacks I supplied xsi:type="xsd:string" on all output
parameters,
and then parsed and ignored any incoming "type"s.. and assumed strings since
everything in Perl is a string anyway..:-)

-Steve



  -----Original Message-----
  From: James Snell [mailto:jsnell@lemoorenet.com]
  Sent: Thursday, August 10, 2000 10:24 PM
  To: soap-dev@xml.apache.org
  Subject: RE: xml-soap and xsi:type requirements


  Right now, nope, there's no way to turn it off right now.  A couple of
ideas have been dicussed, but nothing acted upon yet, and I'm way too
overloaded to make the changes myself.

  - James
    -----Original Message-----
    From: Brown, Keith [mailto:KBrown@develop.com]
    Sent: Thursday, August 10, 2000 6:58 PM
    To: 'soap-dev@xml.apache.org'
    Subject: xml-soap and xsi:type requirements


    It's not clear to me why the Apache implementation requires xsi:type
attributes describing *all* parameters. Is there a way to turn off this
requirement? This would make it much easier to interop with environments
(like Perl) where type information is much more scarce (and not terribly
desirable). I'm guessing the reason for the requirement is for dealing with
overloaded method signatures?

    Following is a thread I posted to the SOAP list recently for some
background.

    Keith

    -----Original Message-----
    From: Brown, Keith [mailto:KBrown@DEVELOP.COM]
    Sent: Thursday, August 10, 2000 3:44 PM
    To: SOAP@DISCUSS.DEVELOP.COM
    Subject: [SOAP] SOAP/Perl progress report


    I'm testing SOAP/Perl against the apache xml-soap implementation, and I
now see what you mean about type-encoding each element. They reject any
requests that don't have xsi:type attributes on all of the parameters.

    I hacked my code to send all parameters as xsd:string, and now I get a
fault code of
    <faultstring>org/apache/soap/util/MethodUtils$MoreSpecific</faultstring>

    which seems to indicate that I need to specify the actual types as
opposed to strings (or just use strings in all my test snippets ;-)

    This isn't looking good from a Perl programmer's perspective - we don't
have that sort of type information in Perl.

    Can anybody on the apache team help me here?

    Keith
      -----Original Message-----
      From: Steven McDowall [mailto:sjm@APTEST.COM]
      Sent: Tuesday, August 08, 2000 8:06 AM
      To: SOAP@DISCUSS.DEVELOP.COM
      Subject: Re: [SOAP] SOAP spec 1.1 and SOAP/Perl 0.23?


      Hmm..How "compliant" is the question .. To which version?

      Are you (which I did) going to type encode each element as
      xsi:type="xsd:string" so it works with an apache SOAP server?

      with the proper constants, etc?

      Just wondering

      -Steve

Mime
View raw message