Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-1590

WebService Proxy - A one-way message that throws exception should not return HTTP code 500

    XMLWordPrintable

    Details

    • Release Notes Text:
      Hide
      https://issues.jboss.org/browse/SOA-1590

      When the Web Service proxy is used to invoke any method it will return the response as provided by the target webservice. In some instances the target webservice may return a response which is not valid within the invoking context. The Web Service proxy does not sanitise these responses and will pass the response back to the caller.
      Show
      https://issues.jboss.org/browse/SOA-1590 When the Web Service proxy is used to invoke any method it will return the response as provided by the target webservice. In some instances the target webservice may return a response which is not valid within the invoking context. The Web Service proxy does not sanitise these responses and will pass the response back to the caller.
    • Release Notes Docs Status:
      Documented as Known Issue

      Description

      Whe WebService proxy is used to invoke one-way web service that thros a runtime exception then the error code 500 is returned to client together with fault message. According to WS-I profile

      The HTTP response to a one-way operation indicates the success or failure of the transmission of the message. Based on the semantics of the different response status codes supported by the HTTP protocol, the Profile specifies that "200" and "202" are the preferred status codes that the sender should expect, signifying that the one-way message was received. A successful transmission does not indicate that the SOAP processing layer and the application logic has had a chance to validate the envelope or have committed to processing it.

      Only 200 or 202 codes should be returned as the message was successfully transmitted to JBossESB and code 500 should not be used to report errors at service level.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dlesage David Le Sage
                  Reporter:
                  jpechanec Jiri Pechanec
                  Writer:
                  David Le Sage
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: