Re: Cont: upgrading cxf client to 3.0.1

[edbras <no...@debrasjes.com>]

It have been a while, but I just found out that I solved the issue by
disabling Mtom:
      	 
Then it works... ;)....
Any idea why this solved the issue ? (I am trying CXF 3.1.4 currently).
And how is it possible to solve this with mtom enabled ?

The issue was:
The Webservice response contained the MIME type, such that the xml parser
complaints:
---------
--uuid:cacb0df1-911c-4440-bdf6-e7b6bfcaa5e1
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-ID: <ro...@cxf.apache.org>

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/....
.....
---------

=========Exception stacktrace (see details in other post):
------
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected 
character '-' (code 45) in prolog; expected '<' 
at [row,col {unknown-source}]: [3,1] 
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:64 
7) ~[woodstox-core-asl-4.4.0.jar:4.4.0] 
------



--
View this message in context: http://cxf.547215.n5.nabble.com/Cont-upgrading-cxf-client-to-3-0-1-tp5748543p5763995.html
Sent from the cxf-user mailing list archive at Nabble.com.