Hi Chamikara,
I don't know why the code is trying to reuse the request side Options
object, just that it is and that it is is marked in the code with:
// This is a hack - Needs to change
Which suggests that it's being done for a conscious reason but I can't
work out what it is. If someone can explain it I'll be more that happy
to try to do a better fix.
Can anyone shed any light on this?
David
On 23/08/06, Chamikara Jayalath <[EMAIL PROTECTED]> wrote:
Hi David,
What is the reason for trying to use the request-side options object for
the response side as well. What prevents us from creating a new one.
Current code makes is impossible to use the same options object for several
invications. For example following code will not work
<code>
Options options = new Options();
//set action and other properties to the options object.
serviceClient.setOptions (options);
serviceClient.sendReceive ();
serviceClient.sendReceive ();
</code>
Options object have to be re-filled after every invocation.
Chamikara
On 8/23/06, David Illsley <[EMAIL PROTECTED]> wrote:
>
Hi Chamikara,
I added that because the Options object is reused so soapAction needs
to be removed so that soapAction+wsa:Action on response don't conflict
(because if they do the addressing in handler will fault).
It may not be strictly required when isUseSeparateListener is set but
is required when doing sync and the response message context has the
same options object set (see line 367) and I thought retaining the
same behaviour for when isUseSeparateListener has both values was
better. A better solution would be to fix the line 349 which is
described as
// This is a hack - Needs to change
but I didn't know how to do this becuase I couldn't work out what it
was a hack around!
I'm happy to fix up the options reuse problem if someone can explain
the hack to me and what needs to be done though I'm heading off this
evening for a few days without a computer so I can't do it before
Tuesday.
Cheers,
David
On 23/08/06, Chamikara Jayalath <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> A small question regarding the line 284 of OutInAxisOperation,
>
> options.setAction("");
>
> This seems to be resetting the action value everytime a message is sent.
Is
> this a requirement.
> Because of this the client has to set the action repeatedly in every
> invocation (even for the same options object).
>
>
> Chamikara
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
