Created attachment 573063 [details] Server log Seam version: 2.2.5.EAP5 (included in EAP 5.1.2.GA) The seambay example from Seam 2.2 was migrated to EAP6 according to the migration guide on Documentation-Stage (http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Beta_Documentation/Migrate_Seam_22_Archives_to_JBoss_Enterprise_Application_Platform_6.html) and the bug was verified to occur with EAP 6.0.0.ER2. Note: the seambay example ftests first fail due to this issue: https://issues.jboss.org/browse/JBPAPP-8322 After JBPAPP-8322 is patched, the following problem unfolds: The createNewAuctionTest (or possibly some other, depending on execution order) fails with a NotLoggedInException. It appears the main cause is the conversation ID not being propagated in SOAP requests by org.jboss.seam.webservice.SOAPRequestHandler. There is a patch for this problem: https://gist.github.com/1996490 The ftest fails with: [testng] FAILED: createNewAuctionTest [testng] java.lang.AssertionError: Response area should contain information about creating the auction. Relevant part of server log attached.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The cause of this issue is the SOAP message header being null when processing the message in the SOAPRequestHandler and consequently, the conversation ID not being set. This issue can be worked around by overriding org.jboss.seam.webservice.SOAPRequestHandler.handleOutbound, as described in https://issues.jboss.org/browse/JBPAPP-8376.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1,13 @@ -The cause of this issue is the SOAP message header being null when processing the message in the SOAPRequestHandler and consequently, the conversation ID not being set. +The Seambay ftest fails with a NotLoggedInException because the SOAP message header is null when processing the message in the SOAPRequestHandler and the conversation ID not being set. -This issue can be worked around by overriding org.jboss.seam.webservice.SOAPRequestHandler.handleOutbound, as described in https://issues.jboss.org/browse/JBPAPP-8376.+This issue can be worked around by overriding org.jboss.seam.webservice.SOAPRequestHandler.handleOutbound. Procedure 2.1 details how to do this. + +1. Create a file named SOAPRequestHandlerAS7.java and place it in SEAMBAY_EXAMPLE/src/org/jboss/seam/example/seambay with the following contents: + +<snipped code for brevity; it comes from the related JIRA> + +2. Register the JAX-WS handler by: + +<snipped code for brevity; it comes from the related JIRA> + +3. Reference the file from the web service implementation (AuctionService in this case) by annotating the class with @HandlerChain(file="../../../../../seam-jaxws-handlerchain.xml").
Seam 2.2 certification is a part of WFK 2.0.0.
Marek Novotny <mnovotny> updated the status of jira JBPAPP-8376 to Resolved
Rajesh Rajasekaran <rajesh.rajasekaran> updated the status of jira JBPAPP-8376 to Closed
Rajesh Rajasekaran <rajesh.rajasekaran> made a comment on jira JBPAPP-8376 Marking "Won't fix", "Rejected" and "Out of Date" items as CLOSED.
Marek Novotny <mnovotny> updated the status of jira JBPAPP-8376 to Reopened
Marek Novotny <mnovotny> made a comment on jira JBPAPP-8376 Reopening because this seems like an issue in implementation of SOAPRequestHandler. SOAPHeader is used by Seam for storing conversation ID and it is IMO wrongly ignored when SOAPHeader is not in SOAP message.
Marek Schmidt <maschmid> updated the status of jira JBPAPP-8376 to Closed
Marek Schmidt <maschmid> made a comment on jira JBPAPP-8376 Verified with Seam from EAP 5.2.0.ER4 on EAP 6.0.1 ER3