JAXB2 response validation produces non well-formed response in case of a
non-valid response
-------------------------------------------------------------------------------------------
Key: XFIRE-963
URL: http://jira.codehaus.org/browse/XFIRE-963
Project: XFire
Issue Type: Bug
Components: Core
Affects Versions: 1.2.5
Reporter: Yves
Assignee: Dan Diephouse
I have enabled response validation for my webservice with JAXB2 binding. In
case of a non-valid response the JAXB2 marshaller throws the expected error but
on the wire you get a non-wellformed response with HTTP code 200. It seems that
XFire already begins to stream the soap part of the response and detects the
marshalling problem too late:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=UTF-8
Transfer-Encoding: chunked
Server: Jetty(6.1.0pre0)
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soap:Body>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Could not marshall type.</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
