OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [regrep] WSDL Issues


I have to ask why you elected to use rpc/literal. Very few SOAP
implementations currently support rpc/literal. Why not just use
document/literal?

Regards,
Anne

----- Original Message -----
From: "Farrukh Najmi" <farrukh.najmi@sun.com>
To: <regrep@lists.oasis-open.org>
Cc: "matt" <matt@yellowdragonsoft.com>
Sent: Tuesday, June 24, 2003 9:58 AM
Subject: [regrep] WSDL Issues


> Team,
>
> I have just become aware of a few minor issues in our WSDL for 2.5 (see
> message below). The first is that we have some alignment issues with
> WS-I basic profile. The second is an actual WSDL bug.
>
> Matt will you be able to look into the issues listed below and do a
> surgical fix on our WSDLs for version 2.6? Thanks in advance for your
> help. Let me know if I can help. Thanks.
>
> --
> Farrukh
>
> -------- Original Message --------
>
> Hi Farrukh,
>
> Whats happening is, there are multiple imports of same schema document,
> for example rs.xsd is imported using wsdl:import from a WSDL document
> and using xsd:import from inside different schema documents. This is
> legal. The check for duplicate entity seems to have bug when wsdl:import
> importing schema and the same schema is imported from xsd:import.
>
> workaround:
>
> one of the WSDL (ebXMLRegistrySOAPService.wsdl) is not WS-I BP
> conformant. Making it conformant will correct this error.
>
> So the workaround will be to import schema document only from within
> <xsd:schema>. This is as per WS-I BP 1.0 -
>
http://ws-i.org/Profiles/Basic/2003-05/BasicProfile-1.0-WGAD.htm#refinement4
3303408,
> R2001/R2002. I am not sure if you can edit the WSDL,
>
http://www.oasis-open.org/committees/regrep/documents/2.5/services/ebXMLRegi
strySOAPService.wsdl.
>
> add -f:wsi option to wscompile and you will see the warning about this.
>
> Regardless, this is a bug as jaxrpc allows schema document import using
> wsdl:import. So go ahead and file a bug for this duplicate entity error.
>
> Additionally, this WSDL is incorrect. The biding is rpc/lit, however
> <wsdl:message part has element attribute and not type. This results in
> wscompile ignoring the associated operations.
>
> for example:
>
> <message name="msgRegistryResponse">
>         <documentation>Defines a RegistryResponse message.</documentation>
>         <part name="partRegistryResponse" element="rs:RegistryResponse"/>
>         <part name="partContent" type="xsd:string"/>
> </message>
>
> should be:
>
> <message name="msgRegistryResponse">
>         <documentation>Defines a RegistryResponse message.</documentation>
>         <part name="partRegistryResponse" type="rs:RegistryResponseType"/>
>         <part name="partContent" type="xsd:string"/>
> </message>
>
>
> --
> Farrukh
>
>
>
> You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
php
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]