Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5710

[JBossWS] content-type header is not properly set for FastInfoset response messages

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • None
    • Web Services
    • None
    • Hide
      When a request with an application/fastinfoset content-type header was sent to the FastInfoset web service, the response was returned with an incorrect header of application/soap+xml or text/xml. This issue has been corrected with an upgrade of the JBoss Web Services component.
      Show
      When a request with an application/fastinfoset content-type header was sent to the FastInfoset web service, the response was returned with an incorrect header of application/soap+xml or text/xml. This issue has been corrected with an upgrade of the JBoss Web Services component.
    • Documented as Resolved Issue

    Description

      The content-type mime header is properly set to application/fastinfoset in request messages, but is still set to application/soap+xml or text/xml for response.

      This is fixed in the jbossws-native-4.0 mentioned in the jira https://issues.jboss.org/browse/JBWS-3192.

      We need to port the changes to the eap maintenance branch https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-3.1.2

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-4552 Release and upgrade JBossWS Native

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBWS-3192 content-type header is not properly set for FastInfoset response messages

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-ghu Gary Hu
              rhn-support-ghu Gary Hu
              Laura Bailey Laura Bailey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: