Bug 807306
| Summary: | Seambay ftest fails with NotLoggedInException | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Ron Šmeral <rsmeral> | ||||
| Component: | Seam | Assignee: | Marek Novotny <mnovotny> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondrej Skutka <oskutka> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2.0.0.GA | CC: | amelicha, kpiwko, rnewton | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | Seam2.2 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
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. 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").
|
Story Points: | --- | ||||
| Clone Of: | Environment: |
Fedora 16 64-bit, Mozilla Firefox 3.6.25, Oracle JDK 1.6.0_30, Seam 2.2.5.EAP5 (included in EAP 5.1.2.GA)
|
|||||
| Last Closed: | 2012-06-19 08:18:05 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ron Šmeral
2012-03-27 13:19:57 UTC
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 Novotny <mnovotny> updated the status of jira JBPAPP-8376 to Resolved 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 |