Peoples, 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. Thank you, John.
John and all, I disagree on a single WSDL file. WSDL should be separated by each role. Actually, G-lambda-AIST team has developed a requester library for ultimate requesters, which implements the Requester WSDL only. In addition, it is easy to implement both interfaces. Thank you, Atsuko. 2012/4/12 John MacAuley <john.macauley@surfnet.nl>:
Peoples,
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.
Thank you, John. _______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
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
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@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
Hi John,
If we combine these into a single space then this issue of handling exceptions separately goes away.
for the Harmony interface specification we extracted common types and exceptions into a separate XSD that was included in the two different XSDs. That might be a valid approach. Best regards, Alex On 13.04.2012, at 16:07, John MacAuley wrote:
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@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
-- av.tu-berlin.de/willner
The common types are in a separate file at the moment. It seems to be related to JAX-WS compile rules when generating the stubs for the soap operations. It creates a set of types in context of the provider or requester namespace. Thank you, John On 2012-04-13, at 10:31 AM, Alexander Willner <alexander.willner@tu-berlin.de> wrote:
Hi John,
If we combine these into a single space then this issue of handling exceptions separately goes away.
for the Harmony interface specification we extracted common types and exceptions into a separate XSD that was included in the two different XSDs. That might be a valid approach.
Best regards, Alex
On 13.04.2012, at 16:07, John MacAuley wrote:
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@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
-- av.tu-berlin.de/willner
participants (4)
-
Alexander Willner -
Atsuko Takefusa -
Henrik Thostrup Jensen -
John MacAuley