← Prev in month ← Prev in thread

WS RM Fault Codes

From
Runil Lunisetty
Date
2004-01-14T23:49:08+00:00
ID
Thread
WS RM Fault Codes
This proposal lists the fault codes to be sent in the RM Fault Headers.
Note that SOAP 1.1 disallows using the <fault:detail> element to send
faults that happen during the processing of Headers. Such faults should
be send in SOAP Headers itself.

This exercise is for SOAP 1.1 msgs. only. A SOAP 1.2 version will be
done at a later stage.

Invalid Msg. Format Faults:

InvalidGroupId: This fault is sent if the GroupId format is wrong or invalid

InvalidRefToGroupId: This fault is sent if the RefToGroupId format is wrong
or invalid.

InvalidSequenceNumber: This fault is sent if the SequenceNumber format
is wrong or invalid The same fault is sent if the value of status attribute
is not of begin|continue|end.

InvalidRefToSequenceNumberRange: This fault is sent if the RefToSequenceNumberRange 
format is wrong or invalid

InvalidExpiryTime: This fault is sent if the ExpiryTime format is wrong
or invalid

InvalidReplyPattern: This fault is sent if the ReplyPattern  format
is wrong or invalid or when the replyTo attribute is missing for the Callback
pattern.

InvalidGroupParameters: This fault is sent for any of these cases:

groupExpiryTime is wrong or invalid

groupMaxIdleDuration is wrong or invalid

when both group parameters are present

when groupExpiryTime decreases for a subsequent msgs. in an ordered group

InvalidMessageHeader: This fault is sent when the MessageHeader element
is wrong or invalid. Examples are:

When one of the mandatory elements (GroupId, ExpiryTime, ReplyPattern)
is missing

InvalidPollRequest

When GroupId is missing

When SequenceNumberRange element is wrong or invalid

Faultcode for all the above faults should be env:Client.

Request Processing Faults:

RequestProcessingFault: This fault is thrown by the receiving RMP when
it cannot process the request for any of the following cases:

It doesn’t support the ReplyPattern sent by the Sender

Doesn’t support any of the RM agreement items

Persistence problems

Cannot send an Ack.

Faultcode for the above fault should be env:Server.
← Prev in month ← Prev in thread