[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBCORE-1) New features for MSH signal overrides for both packageId and channelId. Document how the MSH signal package and channel is determined.
[ https://issues.oasis-open.org/browse/EBCORE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65042#comment-65042 ]
Pim van der Eijk commented on EBCORE-1:
---------------------------------------
Restarting the JIRA to handle the finalization of CPPA3, a couple of comments:
On the main comment (channels for signals), in CPPA3, errors and receipts have their own channels. There is not a single channel for a party. So it is possible to specify to fully configure them. Also, the channels for user messages have their own error and receipt specifications. So for different types of actions, different error and receipt channels can be specified. This works for ebMS3 as well as for ebMS2, and for ebMS2 it solves all the issues that CPPA2 had with this.
On 1) the current draft CPPA3 does not yet have a default business channel. It could add some further simplification for simple CPPs/CPAs. If we wanted one, we should have a default channel for sending and receiving, as the CPPA3 channels no longer have a "sending" and a "receiving" side.
On 2) this is now solved. Any type of exchange (even protocol-specific types of exchanges) can have their own channels configured.
On 3) CPPA3 covers all of ebMS3 and AS4.
On 4) CPPA3 covers all of ebMS3 Part 2 (except for the two SecureConversation parameters) including multi-hop.
> New features for MSH signal overrides for both packageId and channelId. Document how the MSH signal package and channel is determined.
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EBCORE-1
> URL: https://issues.oasis-open.org/browse/EBCORE-1
> Project: OASIS ebXML Core (ebCore) TC
> Issue Type: Improvement
> Components: CPPA
> Environment: CPPA Version 3
> Reporter: Dale Moberg
> Assignee: Pim van der Eijk
>
> [From pvde]
> The problem was that an asynchronous MSH signal, like an acknowledgment, must be signed in all cases where ackSignatureRequested is set to true and never signed in cases where it is set to false. The MshDeliveryChannel allows to select a particular channel for the asynchronous acknowledgment, so a channel that uses or doesn't use signing can be selected as appropriate. It would be a child element of ThisPartyActionBinding.
>
> If the MshDeliveryChannel is omitted, and if there is an OverrideMSHChannelId for Acknowledgment messages, the channel specified there would be used. If the MshDeliveryChannel is omitted and there is no OverrideMSHChannelId for Acknowledgment messages, the channel indicated by defaultMSHChannelId would be used.
>
> So on re-reading the proposed text, the first bullet should be split in two separate bullets:
>
> - If the MshDeliveryChannel element is not present, but there is an OverrideMSHChannelId for acknowledgment messages, the OverrideMSHChannelId value will be used.
> - If the MshDeliveryChannel element is not present and there is no OverrideMSHChannelId for acknowledgment messages, the defaultMSHChannelId value will be used.
> Finally was there to be an override permitted for defaultMshPackageId?
>
> I'm not sure, probably not if this is just about a SOAP header that has or doesn't have a WSS header in it.
>
> Related questions/comments:
>
> 1) While looking at CPA and channels, here is a suggestion for a default business channel:
> http://lists.oasis-open.org/archives/ebxml-cppa/200606/msg00009.html
>
> It could be useful for simple CPAs where e.g. all/most business messages use the same channel.
> Easy to spec, easy to implement, results in more readable CPAs.
>
> 2) For ebMS 3.0, we need to configure channels for the Receipt NRR Signals. These may be used with or without WS reliable messaging, may use the same channels as WS-R* acknowledgments or different ones, and may be signed or not independently from whether or not the WS-R* acknowledgments are signed. Should we have an attribute ReceiptDeliveryChannel too?
>
> 3) Do you plan to also cover AS4 configuration with CPA 3.0? It has a few extra P-modes.
>
> 4) Do you plan to also cover ebMS 3.0 with multihop with CPA 3.0? As the multihop profile is nearing completion, it would be great if CPA 3.0 supported it.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]