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

FaultMessageResolver should not be constrained to IOExceptions

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0 RC2
    • Fix Version/s: 1.0
    • Component/s: Core
    • Labels:
      None

      Description

      The resolveFault(WebServiceMessage) method of the org.springframework.ws.client.core.FaultMessageResolver interface declares an IOException to be thrown, effectively constraining any implementations to throw either subclasses of IOException or RuntimeExceptions. Is there any reason why it should not be allowed to throw any type of Exception?

        Activity

        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        If the faultresolver would also be able to throw checked exceptions, then these would propagate to the template, meaning that all methods on the template would also throw Exception. This is not the general pattern that people expect when using a template (cf. JdbcTemplate, JmsTemplate, etc): these only throw RuntimeExceptions.

        Show
        arjen.poutsma Arjen Poutsma added a comment - If the faultresolver would also be able to throw checked exceptions, then these would propagate to the template, meaning that all methods on the template would also throw Exception. This is not the general pattern that people expect when using a template (cf. JdbcTemplate, JmsTemplate, etc): these only throw RuntimeExceptions.
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Closing issues for 1.0.0

        Show
        arjen.poutsma Arjen Poutsma added a comment - Closing issues for 1.0.0

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            hudalla Kai Hudalla
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: