Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-850

NoEndpointFoundException swallowed by WebServiceMessageReceiverObjectSupport


    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1.3
    • Fix Version/s: 2.2.RC1
    • Component/s: Core
    • Labels:


      Most HTTP level exceptions, such as XML parsing issues, can be handled by writing a custom WebServiceMessageHandlerAdapter that converts them to, for example, SOAP faults. However, NoEndpointFoundException is swallowed by WebServiceMessageReceiverObjectSupport class so that it is not thrown:

      catch (NoEndpointFoundException ex) {
      if (connection instanceof EndpointAwareWebServiceConnection)

      { ((EndpointAwareWebServiceConnection) connection).endpointNotFound(); }


      this is in final method handleConnection(), so it cannot be overridden either. Instead, a handle adapter must re-implement this whole method if NoEndpointFoundException is wanted to be converted to SOAP Fault. Either the exception should be re-thrown or there needs to be an extension point.


        slsh Jarkko Rantavuori created issue -
        arjen.poutsma Arjen Poutsma made changes -
        Field Original Value New Value
        Assignee Arjen Poutsma [ arjen.poutsma ]
        arjen.poutsma Arjen Poutsma made changes -
        Fix Version/s 2.1.5 [ 14349 ]
        arjen.poutsma Arjen Poutsma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        arjen.poutsma Arjen Poutsma made changes -
        Fix Version/s 2.2 [ 12850 ]
        Fix Version/s 2.1.5 [ 14349 ]


          • Assignee:
            arjen.poutsma Arjen Poutsma
            slsh Jarkko Rantavuori
          • Votes:
            0 Vote for this issue
            2 Start watching this issue


            • Created: