Fwd: WSDL/XSD limitation?

[Alex Ceponkus <alex@ceponkus.org>]

Attached below:  A post to the Yahoo WSDL group describing the WSDL/XSD
problem with the btp:messages wrapper.  No good solution was posted.
Some people had contacted me privately that they have tried something
similar in the past with no luck.

Perhaps somebody on this list has a solution?

Alex


> -----Original Message-----
> From: Alex Ceponkus [mailto:alex@ceponkus.org]
> Sent: Monday, January 20, 2003 8:21 PM
> To: wsdl@yahoogroups.com
> Subject: [wsdl] WSDL/XSD limitation?
>
>
> I have a document/literal SOAP service that I am trying to describe in
> WSDL, but not sure if such a WSDL is possible.
>
> The service accepts two different documents for the request:
>
> <SOAP-ENV:Body>
>   <foo>
>    <a>...</a>
>   </foo>
> </SOAP-ENV:Body>
>
> or
>
> <SOAP-ENV:Body>
>   <foo>
>    <b>...</b>
>   </foo>
> </SOAP-ENV:Body>
>
> I can easily expose a WSDL operation (let's call it 'foo-operation')
> that has element 'foo' as the input.  The schema defines the element
> 'foo' and its children 'a' or 'b'.
>
> However, I want to be able to expose two operations: 'fooa-operation'
> and 'foob-operation', that take foo/a and foo/b, respectively, as the
> inputs.  A developer interested in 'fooa' should be able to drop this
> WSDL into their favourite WSDL toolkit and generate a client that puts
> <foo><a> on the wire.  Not a <foo> with either <a> or <b> as children.
> Since the schema can only contain one <foo> element from a given
> namespace, I do not believe this is possible without creating a separate
> WSDL for each operation.  Each operation needs to provide a different
> (constrained) view of the schema.
>
> I hope somebody will point out an obvious oversight on my part. :)  Any
> ideas appreciated!
>
> Regards,
> Alex
>