MConnection MEP

Hi all,

Some recent investigation has revealed that Sandesha2 treats a 
MakeConnection msg as a 2-way msg.
However, according to the MC spec this is not entirely correct:

"The MakeConnection element is sent in the body of a one-way message that 
establishes a contextualized back-channel..."

The time that this becomes an issue is when WS-A is involved. Obviously we 
need a replyTo for MC connection to be any use to us. However, by defining 
MConnection as a 2-way we find that WS-A will complain if there is no 
msgID present in the msg. 
This is causing interop issues, since there is really no requirement on 
there being a msgID in this case.

So our options are to define the msg as 1-way or to perform some sort of 
"ignore the WSA msgID restriction in this specific case" fix.

I'm happy with either. One issue with making the MConnection msg 1way is 
that this breaks the sandesha unit tests: we stop sending spec defined 
faults back (e.g. "missing selection criteria" etc) due to code in axis2 
org.apache.axis2.receivers.AbstractMessageReceiver which swallows the 
fault in the case of a one way MEP.
Can this be changed?

Any thoughts on this issue would be gratefully appreciated. 

Many thanks,
Thomas

----------------------------------
Thomas McKiernan

WebSphere Messaging Development,
IBM United Kingdom Limited

Internal Phone: 248241 
External Phone: +44 (0)1962 818241
Mobile: +44 (0)789 1737497
Email: [email protected]

Mail Point 211, IBM, Hursley Park, Winchester, Hampshire, England, SO21 
2JN


Caminante, no hay camino 
Se hace camino al andar.
("Walker, there is no path; the path is made by walking.")  Antonio 
Machado





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU