Uploaded image for project: 'ServiceMix'
  1. ServiceMix
  2. SM-433

Issue in the way servicemix handle soap errors

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0-M2
    • servicemix-http
    • None
    • Servicemix 3.0 ALL

    Description

      With the current version of servicemix (3.0) , my soap fault message is replace by the following HTTP error message:
      ------
      <html>
      <head>
      <title>Error 500 Unknown Error</title>
      </head>
      <body>
      <h2>HTTP ERROR: 500</h2>
      <pre>Unknown Error</pre>
      <p>RequestURI=/Service/</p>
      <p>
      <i>
      <small>
      <a
      href="http://jetty.mortbay.org">Powered by
      Jetty://</a>
      </small>
      </i>
      </p>
      </body>
      </html>


      because of this message, my generated stubs cannot
      properly handle the soap message.
      -------
      The best solution would be to have my soap fault message return to the calling client "as is" so all my business rules can be handle.

      After a few discussion with Guillaume, I've come up with a solution that handle sthe soap faul correctly, what this does is to no longer return an HTTP error message when we get a soap fault on the provider processeur. The soap fault is send as a property of the message to the consumer endpoint who then rebuild the soap fault (and does the conversion (1.1 <-> 1.2) if required.

      Ps : The conversion from 1.1 -> 1.2 is not handle in this code (I had not quick means of testing it).

      Attached are the modified files : ConsumerProcessor.java, ProviderProcessor.java

      Attachments

        Activity

          People

            gnodet Guillaume Nodet
            ewrick Eric Dofonsou
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: