Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0 M1
    • Fix Version/s: 1.0 M2
    • Component/s: Core
    • Labels:
      None

      Description

      From the forum (http://forum.springframework.org/showthread.php?t=25854):

      The org.springframework.ws.transport.http.MessageHandlerAdapter relies on J2EE 1.4 (Servlet 2.4) functionality. When using it under J2EE 1.3, the following exception occurs:

      org.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse: method setCharacterEncoding(Ljava/lang/String;)V not found
      java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse: method setCharacterEncoding(Ljava/lang/String;)V not found

      This should be fixed.

        Activity

        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        The best solution would be to let the SoapMessage write itself to a HttpServletResponse, since the message has all of the necessary mime headers avilable.

        Show
        arjen.poutsma Arjen Poutsma added a comment - The best solution would be to let the SoapMessage write itself to a HttpServletResponse, since the message has all of the necessary mime headers avilable.
        Show
        arjen.poutsma Arjen Poutsma added a comment - This is fixed in svn ( https://svn.sourceforge.net/svnroot/springframework/spring-projects/trunk/spring-ws/ )

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            arjen.poutsma Arjen Poutsma
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: