Hang on a bit.
Ok, I agree to include this property. But we need to do following while
implementing it.
1. Once this property is set, user _MUST_ set a replyTo EPR
2. When this property is set and when user sets a replyTo epr, what if
the reply never comes back to the same Callback? Then we need to handle
this properly.
3. How will RM or anyone who sets the replyTo epr hand over the response
message to the Callback object?
Thanks,
Chinthaka
Chamikara Jayalath wrote:
Hi Chinthaka,
OK.
As u mentioned in ur previous mail currently the semantics of
isUseSeperateListner=true has two things.
1. Don't use the back channel of the request message to build the response.
2. Mr. Axis2, please manage the second channel for me.
Now what I want it someway to only give the first semantic. I.e. the
second channel will be managed by my own manner (for e.g. RM polling).
I believe this is a general requirement.
My sugestion is to introduce a new property to the options object named
DONT_USE_AXIS2_LISTNER (please suggest a different name if this sounds bad).
If this property is not set execution will be done as it is currently
implemented. But if it is set to 'true' Axis2 will not start its listner
and will allow user to set what ever the replyTo value he wants.
Hope this clarifies.
Chamikara
On 9/27/06, *Eran Chinthaka* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Chamikara,
Before you do the change, can you please be kind enough to summarize
the
change you gonna do?
Thanks,
Chinthaka
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
