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

AxiomSoapMessageFactory throws IllegalArgument when Content-Type is not set

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.5.6
    • Fix Version/s: 1.5.7
    • Component/s: Core
    • Labels:
      None
    • Environment:
      IBM Wensphere 6.1, MQ (JMS), Oracle

      Description

      Messages recieved must contain the header "Content-Type" when the header does not contain this a IllegalArgument exceptions is thrown, "TransportInputStream contains no Content-Type header".
      Though this is correct is the pure sense, there is no real specification for sending messages by means of MOM.

      When the sender of the message is Spring-WS this does not impose any problems (the header is set) but when others, in our case Oracle BPM, sends a message the header is not send and where not able to process the response.

      Possible solution, assume a default value for the "Content-Type" header is message from the MOM. content-type=text/xml?

        Activity

        pieni Pieter van der Meer created issue -
        arjen.poutsma Arjen Poutsma made changes -
        Field Original Value New Value
        Original Estimate 0.25d [ 7200 ]
        Fix Version/s 1.5.7 [ 11173 ]
        Remaining Estimate 0.25d [ 7200 ]
        Hide
        arjen.poutsma Arjen Poutsma added a comment - - edited

        Actually, there is a proposed specification for running SOAP over JMS, see http://www.w3.org/TR/2008/WD-soapjms-20081121/, and Spring-WS is among the few implementations (if not the only one): we use the SOAPJMS_contentType JMS property as value for the Content-Type header. This just shows that implementing a spec does not guarantee interoperability, I guess.

        So I will make the Content-Type optional, and default to the standard SOAP 1.1 content-type (text/xml).

        Show
        arjen.poutsma Arjen Poutsma added a comment - - edited Actually, there is a proposed specification for running SOAP over JMS, see http://www.w3.org/TR/2008/WD-soapjms-20081121/ , and Spring-WS is among the few implementations (if not the only one): we use the SOAPJMS_contentType JMS property as value for the Content-Type header. This just shows that implementing a spec does not guarantee interoperability, I guess. So I will make the Content-Type optional, and default to the standard SOAP 1.1 content-type (text/xml).
        arjen.poutsma Arjen Poutsma made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        arjen.poutsma Arjen Poutsma made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Closing old issues

        Show
        arjen.poutsma Arjen Poutsma added a comment - Closing old issues
        arjen.poutsma Arjen Poutsma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        32m 38s 1 Arjen Poutsma 13/May/09 11:11 PM
        In Progress In Progress Resolved Resolved
        3m 14s 1 Arjen Poutsma 13/May/09 11:15 PM
        Resolved Resolved Closed Closed
        1086d 7h 48m 1 Arjen Poutsma 04/May/12 7:03 AM

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            pieni Pieter van der Meer
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: