[
https://issues.apache.org/jira/browse/AXIS2-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931953#comment-17931953
]
Robert Lazarski commented on AXIS2-6061:
----------------------------------------
I agree.
The better fix here would be to customize the fault output in
SOAPMessageFormatter to be text, similar to what is done with JSON in adapting
to that format in JsonFormatter using .
I made a commit to start supporting that by exposing the HTTP response code to
the fault MessageContext.
The problem is that when changing the 404 return format - lots of unit tests
break.
We are starting a release vote this Wednesday and I am lacking a better fix in
time.
> Axis2 client parses soap envolope in case of a http-404
> -------------------------------------------------------
>
> Key: AXIS2-6061
> URL: https://issues.apache.org/jira/browse/AXIS2-6061
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.8.2
> Reporter: Manfred Weiss
> Assignee: Robert Lazarski
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.1
>
>
> If the server returns a 404 with HTML, the client tries to parse a soap
> envelope and fails with:
> {code:java}
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'd' (code
> 100) after '<!' (malformed comment?){code}
> I believe the problem was introduced with this commit:
> [https://github.com/apache/axis-axis2-java-core/commit/93d54beb5186803ea7dcb4a806c88d9ae2ea774f]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
