OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

business-transaction message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue - maint-15 - InvalidSuperior/InvalidInferior Faults used inappropriately


This issue has been added to the btpm issue list with a status of "provisional". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

The issues list is posted as a Technical Committee document to the OASIS BTP TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the BTP TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - maint-15 - InvalidSuperior/InvalidInferior Faults used inappropriately

Status:resolution proposed
Date added: 14 Sep 2004
Date submitted: 14 September 2004
Submitter: Peter Furniss
Description: The existing text states that a Fault of InvalidInferior or InvalidSuperior is returned from messages of the Outcome protocol when the inferior/superior is unknown.

However, for most cases the detailed text and the state tables specify that INFERIOR_STATE/unknown or SUPERIOR_STATE/unknown (as appropriate) is sent, or, for the last message of the Outcome exchange, the incoming message should be ignored.

Similarly, REQUEST_STATUS allows a reply of FAULT/Unknown-transaction, which would seem to be an unecessary synonym for STATUS/unknown.
Proposed resolution: Remove the statements that unecessary Fault values are allowed.

Leave Fault/InvalidInferior as a response where the inferior is not valid for the transaction in question (e.g. on up-tree messages)
Changes: 14 Sep 2004 - new issue


To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the business-transaction@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - maint-15 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - maint-15 - Proposed resolution", without any Re: or similar.

To add a new issue, please email to the issues list maintainer (Peter Furniss).



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]