[
https://issues.jboss.org/browse/JBSEAM-4685?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4685:
---------------------------------------
Well, I understand now why it doesn't work. AS 6 comes with JBossWs-CXF and the
example is configured for JBossWs-Native, therefore
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2/examples/...
is not taken into account in CXF stack. There is 2 options: install JBossWS Native instead
of default CXF stack or provide different configuration for SOAPHandler, which does for
Seam handling of SOAP messages (adding conversationId and restoring conversation)
Unexpected web service response on JBoss AS 6
---------------------------------------------
Key: JBSEAM-4685
URL:
https://issues.jboss.org/browse/JBSEAM-4685
Project: Seam
Issue Type: Bug
Components: WS
Affects Versions: 2.2.1.CR2
Reporter: Jozef Hartinger
Assignee: Marek Novotny
Fix For: 2.2.1.Final
While the login service should return the following response:
<env:Envelope
xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:...
xmlns:seam='http://www.jboss.org/seam/webservice'>3</seam:c...
xmlns:ns2="http://seambay.example.seam.jboss.org/"><retur...
on JBoss 6.0.0 M4, the service returns:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><s...
xmlns:ns1="http://seambay.example.seam.jboss.org/"><retur...
Note the missing conversationId value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira