To Henrik Thostrup Jensen
We confirm that there are correlationID and replyTo elements in the dump of your reservationRequest message.
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").
We modified our implementation to return a serviceException message in case of name space exception.
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.
According to wsdl and schema documents, reservation and its children elements use the following name space defined in ogf_nsi_connection_types.xsd:
xmlns:tns="http://schemas.ogf.org/nsi/2011/07/connection/types"
Could you check out the usage of name spaces for NSI messages?
The following is our example reservationRequest message with ns5 and ns6 name spaces.
<ns5:reservationRequest xmlns:ns2="urn:oasis:names:tc:SAML:2.0:assertion"
xmlns:ns3="http://www.w3.org/2001/04/xmlenc#"
xmlns:ns4="http://www.w3.org/2000/09/xmldsig#"
xmlns:ns5="http://schemas.ogf.org/nsi/2011/07/connection/interface"
xmlns:ns6="http://schemas.ogf.org/nsi/2011/07/connection/types">
<ns5:correlationId>78729d97-8264-4a4b-ad53-8fec5ad529fb</ns5:correlationId>
<ns5:replyTo>http://220.69.240.218:2000/kreonet/ConnectionServiceRequester</ns5:replyTo>
<ns6:reservation>
<requesterNSA>urn:ogf:network:NSnetwork:kreonet</requesterNSA>
<providerNSA>urn:ogf:network:NSnetwork:dynamicKL</providerNSA>
<reservation>
We are waiting for your response.
Thank you.
Best regard.
Hi again
On Fri, 2 Sep 2011, jeonghoon moon wrote:
We found out that ReplyTo and CorrelationID of your reservationRequest message did not have adequate
information.
Please check out those information elements not to be set with “?”.
This is a dump of the SOAP payload I'm sending (I haven't changed the code since the initial request, and still fails the same way):
<SOAP-ENV:Envelope xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/interface" xmlns:ns1="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/>
<ns1:Body>
<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>
<reservation>
<globalReservationId>gid-3228</globalReservationId>
<description>Test Connection</description>
<connectionId>conn-560</connectionId>
<serviceParameters>
<schedule>
<startTime>2011-09-02T09:16:13Z</startTime>
<endTime>2011-09-02T09:18:13Z</endTime>
</schedule>
<bandwidth>
<desired>1000</desired>
</bandwidth>
</serviceParameters>
<path>
<directionality>unidirectional</directionality>
<sourceSTP>
<stpId>urn:ogf:network:stp:Martinique:M1</stpId>
</sourceSTP>
<destSTP>
<stpId>urn:ogf:network:stp:Martinique:M4</stpId>
</destSTP>
</path>
</reservation>
</ns0:reservation>
</ns0:reservationRequest>
</ns1:Body>
</SOAP-ENV:Envelope>
The correlationId and replyTo fields are filled out. I am using an integer representation of the UUID, which might not be "correct" (are you trying to parse it as a UUID, or just using it as a string identifier?).
We upgraded our log site, and you can reach at:
http://220.69.219.228:8080/dynamicKLInfo/dynamicKL.log
Mime type looks good now, but I cannot see any entries from my request.
Thank you for connecting to our web services.
No problem, and thanks for setting it up, so we test it :-).