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

org.jboss.seam.webservice.SOAPRequestHandler doesn't add conversationId if the header is null

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0 ER4
    • EAP_EWP 5.2.0 ER2
    • Seam2
    • None

    • EAP 6.0.1.ER2

    • Hide

      1. Migrate and deploy the seambay example on EAP6.
      2. Run the seambay example functional tests.

      Show
      1. Migrate and deploy the seambay example on EAP6. 2. Run the seambay example functional tests.
    • Release Notes
    • Hide
      The Seam web service integration uses the SOAP header for storing the conversation's ID. However the SOAP header is not mandatory, so attempts by the Seam web service to process a message without a header failed. To resolve this issue the SOAPRequestHandler function now adds a header to any message where the header is missing.
      Show
      The Seam web service integration uses the SOAP header for storing the conversation's ID. However the SOAP header is not mandatory, so attempts by the Seam web service to process a message without a header failed. To resolve this issue the SOAPRequestHandler function now adds a header to any message where the header is missing.
    • Documented as Resolved Issue
    • NEW

      org.jboss.seam.webservice.SOAPRequestHandler doesn't add conversationId if the SOAP header is null. It should create the SOAP header if it doesn't exist yet.

            mnovotny@redhat.com Marek Novotny
            maschmid@redhat.com Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: