Re: [wsrp] [Fwd: Bugs in WSRP v2 WSDL?]

[Rich Thompson <richt2@us.ibm.com>]

These were issues, but are not present
in the present WSDL. It looks like the version Ian is using is from several
drafts ago as it still leveraged the v1 schema and we decided last year
to make the schemas completely separate.

Rich

Michael Freedman <michael.freedman@oracle.com>

02/14/06 12:21 PM

To	wsrp <wsrp@lists.oasis-open.org>
cc	Michael Freedman <michael.freedman@oracle.com>
Subject	[wsrp] [Fwd: Bugs in WSRP v2 WSDL?]

Rich, FYI ...Are these issues?
    -Mike-

----- Message from Ian Penning <ian.penning@oracle.com> on Fri, 10
Feb 2006 18:11:02 +0000 -----

To:	Michael Freedman <michael.freedman@oracle.com>
cc:	Sharmila Jayaram <sharmila.jayaram@oracle.com>, Paul Spencer <paul.spencer@oracle.com>, Michael Gardner <michael.gardner@oracle.com>
Subject:	Bugs in WSRP v2 WSDL?

Hi Mike,

There are a couple of discrepancies between the WSRP draft spec and the
WSDL. According to the spec, the ccppHeaders field on ClientData is optional
(which is what I'd expect) but in the WSDL (wsrp_v2_types.xsd) we have:

  <complexType name="ClientData">
    <complexContent>
      <extension base="v1types:ClientData">
        <sequence>
          <element name="ccppHeaders"
type="types:CCPPHeaders" />
        </sequence>
      </extension>
    </complexContent>
  </complexType>

i.e. ccppHeaders is mandatory. 

Secondly, according to the spec the ccppProfileWarning on MarkupContext
is optional, but in the WSDL we have:

  <complexType name="MarkupContext">
    <complexContent>
      <extension base="v1types:MarkupContext">
        <sequence>
          <element name="ccppProfileWarning"
type="xsd:string" />
        </sequence>
      </extension>
    </complexContent>
  </complexType>

i.e. ccppProfileWarning is mandatory.

Could you check this out and confirm that the WSDL is wrong in both cases?

thanks,
Ian

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php