Profile

Ws-* provides basics like messageId, endpointRef and most importantly, a place for extensions (custom headers). It does not provide though content metadata/desc (ebMS), distinction between signals and user messages, message sequencing and grouping (batch style), boxcarring, optimistic or pessimistic ...

Great enrichment Tim. We achieved multi-hop by implementing WS-Addressing endPointReference extension of Target chains and SOAP UltimateDestination attribute over AS4 profile. Tracking ebMS 3.0 is a good idea. Thx. From: Timothy Bennett To: Derek N LaSalle Cc: 'skiliccote@lbl.gov' ...

We leverage ws-addressing w/ ebMS user and signal message body components. This allows piggy-backing of signal messages with user messages which optimizes flow utilization especially when combined w/ box-carring (message groups). WS-* adherence provides the benefit of widespread development tools and ...

Might I also add, to meet conversational requirements which drive many to use sync request-response, async correlation mechanisms are required in message header and/or payload business content. See BPEL CorrelationSets. From: Derek N LaSalle To: 'bob.old@siemens.com' ; 'ghorst@epri.com' ; ...

Agree that one-way notifications are a dominant pattern especially in financial markets. For performance, when a high QoS delivery semantic is required, optimistic async one notification protocol is at play. This requires session context, idem potency (unique message ids), sequencing, resend/gapfill ...