HTTP nature is offered to outside through the API. Fault sequence here helps us to call the backends(might not be a HTTP service at all), figure out if it sends an error response & then send a proper HTTP error to front end HTTP client (expecting a standard HTTP error code).
On Tue, Jul 23, 2013 at 11:22 AM, Samisa Abeysinghe <[email protected]> wrote: > In the generated API we have a fault sequence. > > In a DevStudio review, the question came, if this was correct to have a > fault sequence, given the HTTP semantics here. > > <api > xmlns="http://ws.apache.org/ns/synapse<http://www.google.com/url?q=http%3A%2F%2Fws.apache.org%2Fns%2Fsynapse&sa=D&sntz=1&usg=AFQjCNHXEm-DVy-kXjma9HiDSOzvmv4DoA>" > name="foo" context="/foo"> > <resource methods="GET"> > <inSequence> > <log/> > </inSequence> > <outSequence> > <log/> > </outSequence> > <faultSequence> > <log/> > </faultSequence> > </resource> > </api> > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- /sumedha b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
