[Nsi-wg] Open dynamicKL NSA
Henrik Thostrup Jensen
htj at nordu.net
Mon Sep 5 05:36:40 CDT 2011
Hi again
On Mon, 5 Sep 2011, Henrik Thostrup Jensen wrote:
> On Sat, 3 Sep 2011, jeonghoon moon wrote:
>
>> In response to your reservationRequest, our implementation locally
>> generated an exception event because of name space problem
>> (xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/interface").
>>
>> The following is a part of SOAP payload from your dump.
>>
>> <ns0:reservationRequest>
>>
>> <ns0:correlationId>315196053139943431651032553079928039634</ns0:correlationId>
>>
>> <ns0:replyTo>http://orval.grid.aau.dk:7080/NSI/services/ConnectionService</ns0:replyTo>
>> <ns0:reservation>
>>
>> <requesterNSA>http://orval.grid.aau.dk:7080/NSI/services/ConnectionService</requesterNSA>
>>
>> <providerNSA>http://220.69.219.228:8010/nsi/ConnectionServiceProvider</providerNSA>
>>
>> We agree to use ns0 for reservationRequest, coorelationID, and replyTo
>> elements.
>>
>> I am not sure whether ns0 name space can be applied to the reservation
>> element or not.
>
> Neither am I. It does look wrong to use the
> http://schemas.ogf.org/nsi/2011/07/connection/interface there. I'll try to
> look into this some more.
Turns out there is a bug in the SOAP/WSDL stack I'm using [1]. Fortunately
there is patch for the problem. Here is the new SOAP envelope:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/types" xmlns:ns1="http://schemas.ogf.org/nsi/2011/07/connection/interface" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns2:Body>
<ns1:reservationConfirmed>
<ns1:correlationId>82084898458119143269587670304668998979</ns1:correlationId>
<reservationConfirmed xmlns="http://schemas.ogf.org/nsi/2011/07/connection/types">
<requesterNSA>http://localhost:7080/NSI/services/ConnectionService</requesterNSA>
<providerNSA>http://localhost:9080/NSI/services/ConnectionService</providerNSA>
<reservation>
<globalReservationId>gid-4372</globalReservationId>
<description>Test Connection</description>
<connectionId>conn-384</connectionId>
<serviceParameters>
<schedule/>
<bandwidth>
<desired/>
</bandwidth>
</serviceParameters>
<path>
<directionality/>
<sourceSTP>
<stpId/>
</sourceSTP>
<destSTP>
<stpId/>
</destSTP>
</path>
</reservation>
</reservationConfirmed>
</ns1:reservationConfirmed>
</ns2:Body>
</SOAP-ENV:Envelope>
This changes the error in the dynamicKL log to concern the providerNSA,
most likely because I don't use the URN scheme (next on the todays todo
list).
Thanks for helping debugging this.
1. https://fedorahosted.org/suds/ticket/292
Best regards, Henrik
Henrik Thostrup Jensen <htj at ndgf.org>
NORDUnet / Nordic Data Grid Facility.
More information about the nsi-wg
mailing list