[BYTEIO-WG] UNICORE client - GenesisEndpoint (apologies and problem found)

My apologies -- now that I look closer at your message, I can see that it is indeed a brand new message (the formatting was so similar to the one before that i mis-read it). I do however see the problem. According to the WS-Addressing SOAP Binding document, the wsa:IsReferenceParameter="true" attribute is spelled with a capital 'I'. Notice that the message that you sent me has a lower-case 'i' instead. I've tested this hypothesis by "echo-ing" your last message back at my service with this change (and new reference parameter value since the last one was deleted) and it works correctly. If you can make this one change, I think you'll find that your client will be able to interoperate with us. Thanks, Mark and Karolina On Fri, 2007-07-27 at 18:23 +0200, Mohammad Shahbaz Memon wrote:

Still getting the same output (size=0) even using the correct soap header.

Cheers

On 7/27/07, Mark Morgan wrote:

...

My apologies -- I did indeed forget to attach last time. Please find the referenced document attached in this message.

Thanks, Mark

On Fri, 2007-07-27 at 16:11 +0200, Mohammad Shahbaz Memon wrote:

...

I couldn't find any attachments in your email. Can you please send this again?

On 7/27/07, Mark Morgan wrote:

...

Mohammad,

The reason that the Size is coming back as 0 is that my service isn't able to identify the resource that you intend to call the operation on. This is because the ReferenceParameters have been incorrectly pasted into the SOAP headers. As per the WS-Addressing SOAP Binding, section 3.4 Binding Message Addressing Properties (http://www.w3.org/TR/2005/CR-ws-addr-soap-20050817/#bindrefp), in order to pass reference parameters from a client to a service endpoint, "the element information item of each of the [reference parameters] (including all of its [children], [attributes] and [in-scope namespaces]) is added as a SOAP header block in the new message". This means that the contents of the ReferenceParameters element (and not the ReferenceParameters element itself) needs to be placed into the SOAP headers. Please find attached a document which shows two example UNICORE to Genesis II SOAP request messages; the first of which is taken from the message trace you sent me earlier, and the latter of which shows that same message modified to remove the ReferenceParameters element and move it's child element (simple-string) directly into the SOAP headers.

-Mark

On Fri, 2007-07-27 at 14:18 +0200, Mohammad Shahbaz Memon wrote:

...

Hi Mark,

Almost all the operations on Genesis II endpoint fails except SbyteIO.GetResouceProperty.

RByteIO: I am successfully getting the resource epr via createResource operation and then upon firing "GetResourceProperty" the response return with Size "0". (Perhaps the file is not created at the time of resource instantiation)

Subsequently, all operation fails as file size is zero.

SByteIO: For debugging, the size of each newly created resource is "0". May be the same problem as with RByteIO.

Attached is the log of only RByteIO invocations for reference.

-- ------------------------------------------------------------------------ Mohammad Shahbaz Memon Department of Applied Mathematics Forschungszentrum Jülich GmbH Jülich Germany

Skype: m.memon Web page: http://www.fz-juelich.de/zam/ZAMPeople/memon_m Office: +49 (0)2461 61 6567 Fax: +49 (0)2461 61 6656 -- byteio-wg mailing list byteio-wg@ogf.org http://www.ogf.org/mailman/listinfo/byteio-wg