It seems to me that the 2.2 MEP section needs to be more
conservative of former MEP distinctions found useful in production and in ebMS
2.0
For example, we used to have a syncReplyMode value to
describe MEP related features in ebMS 2.0
Very popular modes were mshSignalsOnly and none.
In mshSignalsOnly a SOAP request-response MEP was used to
support sending an ebMS user message and receiving back an ack or possibly an
error.
I suppose we will now make use of some form of reliable
messaging in the HTTP response, but we still need a MEP related to the
mshSignalsOnly mode. I am not seeing a candidate here.
For the value “none”, in effect we are saying
that two endpoints are used, and the HTTP response is used at most for SOAP
faults. How does this mode get translated?
For the final committee draft and specification, I would
like to make certain that we lose no ebMS 2.0 functionality with respect to
exchange patterns. All the combinations of syncReplyMode with SOAP over HTTP
need to enabled, and where mshSignals, SOAP faults, and other errors need more
clarity.