If I am in Synapse I am looking at a message on the wire. And I have to decide which way it is going. So in general I have a complex calculation to make:
1. Look at the transport (i.e. is it an HTTP response)
2. See if it has a relatesTo header
3. Look at the To: header (maybe it is anon)
etc.
If it is an In Out* mep, then the In.isResponse=false and the out.isResponse is true for both following messages.
If we have to calculate this every time it will be hard work. I can certainly use setProperty("synapse.response", True) if I want to, but we thought it might be considered an interesting part of the Axis2.MessageContext . However, I won't argue any more :-) I am happy to use a property.
Paul
On 11/11/05, Eran Chinthaka <
[EMAIL PROTECTED]> wrote:
Paul Fremantle wrote:
>Ok folks
>
>1) I will remove processingFault and inFaultFlow.
>2) I think we can remove MessageInformationHeaders from the interface
>3) I'm not sure I agree that the isResponse is never useful in a pure Axis2
>context. Is it not an aspect of a pure SOAP message which direction it is
>going in?
>
>
I think no. The one who handles messages should know that.
1. If you look at a SOAP message on the wire, can you see which
direction it is going ?
2. And if this message context is a part of an IN OUT OUT MEP, which
response are you talking about ? Remember Axis2 can be extended to
support *any* MEP.
In Axis2, You should be able to get this from the message label which
you can get from the AxisOperation.
(If you want an answer of how to implement this functionality in
Synapse, I'd love to answer in Synapse-dev :-) )
-- Chinthaka
