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


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm-interop message

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

Subject: Re: [wsrm-interop] FW: application level faults

As I understand, in WSDL 1.1 you cannot define faults for one-way 
operations. Are we talking about upcoming WSDL 2.0 ?
For the Request-Response scenario I don't think there are doubts of how 
application level faults get back to the sender since it is on the same 
connection, for one way however as it stands there are no application 
faults expected to go back (its one way!). This however will change as 
there is an MEP in WSDL 2.0 where you can define a fault for a one way 

All that being said. Oracle's implementation provides a callback api 
that allows the application to get notifications of things like ultimate 
failure of delivery from the reliability infrastructure and there is no 
reason why those could not be application faults as well.


Bob Freund wrote:

>-----Original Message-----
>From: Mark D. Hansen [mailto:khookguy@yahoo.com]
>Sent: Wednesday, December 17, 2003 2:48 PM
>To: WSRM-Implementers (E-mail)
>Subject: application level faults
>Suppose my RMP-Sender gets an ACK indicating that the message sent has been persisted at the receiving end and is now the responsibility of the RMP-Receiver.
>What if the receiver's application now generates a SOAPFault that is not a WSRM fault?  How should this fault be propagated back to the sender?
>I realize that this is application level communication (not WRSM communication), but is has a lot of practical importance.  
>How are other implementers handling this?

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