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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.2.0 ER2
    • Fix Version/s: EAP_EWP 5.2.0 ER4
    • Component/s: Seam2
    • Labels:
      None
    • Environment:

      EAP 6.0.1.ER2

    • Steps to Reproduce:
      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.
    • Affects:
      Release Notes
    • Release Notes Text:
      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.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

            is related to

            Bug - A problem which impairs or prevents the functions of the product. JBPAPP-8376 Seambay ftest fails with NotLoggedInException

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JBSEAM-4685 Unexpected web service response on JBoss AS 6

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JBSEAM-5104 SoapRequestHandler doesn't create SOAP header if not exists

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  maschmid Marek Schmidt
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: