[Nsi-wg] Combining Provider and Requester WSDL

[John MacAuley]

The value I see from combining really comes down to the handling of the ServiceException.  At the moment, we get one definition in the provider space and one in the requestor space.  When this is run through a JAX-WS compiler I get two class definitions generated, one for the ServiceException in the provider space and one in the requestor space.  If we combine these into a single space then this issue of handling exceptions separately goes away.

I am okay leaving them separate.  I will also play with the ServiceException/SOAP Fault to see if I can remove this dual definition.

John.

On 2012-04-13, at 4:46 AM, Henrik Thostrup Jensen wrote:

> On Wed, 11 Apr 2012, John MacAuley wrote:
> 
>> I know I have been asked by a few of the implementers to combine the Provider and Requester WSDL back into a single file.  I am getting ready to issue a draft of the release 2.0 WSDL and wonder if I could get confirmation to do this. it would definitely simplify my code base if we did this.  Please send in your Yeas and Nays.
> 
> For me it would be easier with a single file (but then again I have it working with multiple now), but I also see Atsukos point.
> 
> Perhaps what we need is one for clients (requester), and one combined/full wsdl for services, which are both providers and requesters (assuming aggregators of course).
> 
> Anyways, I can live with both...
> 
> 
>    Best regards, Henrik
> 
> Henrik Thostrup Jensen <htj at nordu.net>
> Software Developer, NORDUnet
> 
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg