[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (EBXMLMSG-41) PMode[1].ErrorHandling.Report.ProcessErrorNotifyConsumer
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36657#action_36657 ] Sander Fieten commented on EBXMLMSG-41: --------------------------------------- My proposal is to leave this up to an implementation what to do with messages it can not map to a P-Mode. > PMode[1].ErrorHandling.Report.ProcessErrorNotifyConsumer > -------------------------------------------------------- > > Key: EBXMLMSG-41 > URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-41 > Project: OASIS ebXML Messaging Services TC > Issue Type: Improvement > Components: Core Spec > Reporter: Pim van der Eijk > Priority: Minor > > PMode[1].ErrorHandling.Report.ProcessErrorNotifyConsumer: This Boolean parameter indicates whether (if "true") the Consumer (application/party) of a User Message matching this P-Mode should be notified when an error occurs in the Receiving MSH, during processing of the received User message. > This only works if the receiving MSH has been able to map a receiving message to a PMode. The @pmode attribute on AgreementRef is optional and AgreementRef itself is optional. In their absence, a PMode can be inferred from e.g. Service/Action combinations. It should be possible to state how messages that cannot be mapped to a particular PMode are reported and to whom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]