[
https://issues.jboss.org/browse/JBSEAM-4685?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4685:
---------------------------------------
I need to test it with jboss as 4.2.3, if it doesn't break the SOAP handling. Then I
will consider this issue as resolved
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