Hi Eran,
My response is below.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
Eran Chinthaka [EMAIL PROTECTED] wrote on
Brian De Pradine wrote:
I agree with you about your claim on invalid messages being sent by
Axis2, if that is happening now. If that is the case, we need to fix it
in the sending logic and not in dispatchers or message context.
The issue here is not with the sending logic, but with the
Hi Eran,
Please see my comments included below ...
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
Eran Chinthaka [EMAIL
Hi Brian,
Seems to be a good observation. I agree with some of them, but not all :).
The reason behind we keeping endpoint information inside message context
has no direct connection with WS-A. All the information in message
context can be filled by anyone, starting from transport handlers,
Hello all,
Currently, there is a comment in the AddressingFinalInHandler to the
effect that if no wsa:To header is found in an inbound request message
then we do not use the wsa:Anonymous URL as its default value. This is to
allow an alternative, such as the transport URL, to be used instead.
