[
https://issues.apache.org/jira/browse/CXF-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171140#comment-15171140
]
Richard Stollar edited comment on CXF-6805 at 2/29/16 11:19 AM:
----------------------------------------------------------------
There's the problem. I tried to find somewhere where I could set the
property but couldn't work it out.
When the header is set then this is the stack-trace I receive:
*Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[1,1]
Message: Premature end of file.
at
com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:596)
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:1346)
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:1240)
at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:1168)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:219)
... 12 more*
*WSDLManagerImpl.loadDefinition(String url)* must be where things start
to go wrong. I couldn't find where the actual *Message* was being
created in this flow. I'll look at it some more tomorrow. I'm not
really used to working with Maven projects and thus debugging this isn't
something I have tried. I just rebuild the .jar files and re-run my test
application with them - adding System.out.println() messages for debug.
Best regards,
Richard Stollar
------------------------------------------------------------------------
was (Author: stollar):
There's the problem. I tried to find somewhere where I could set the
property but couldn't work it out.
When the header is set then this is the stack-trace I receive:
*Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[1,1]
Message: Premature end of file.
at
com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:596)
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:1346)
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:1240)
at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:1168)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:219)
... 12 more*
*WSDLManagerImpl.loadDefinition(String url)* must be where things start
to go wrong. I couldn't find where the actual *Message* was being
created in this flow. I'll look at it some more tomorrow. I'm not
really used to working with Maven projects and thus debugging this isn't
something I have tried. I just rebuild the .jar files and re-run my test
application with them - adding System.out.println() messages for debug.
Best regards,
Richard Stollar
See: My Site <http://www.stollar.co.uk>
------------------------------------------------------------------------
> cxf-rt-transports-http adds Content-Type header to GET request
> --------------------------------------------------------------
>
> Key: CXF-6805
> URL: https://issues.apache.org/jira/browse/CXF-6805
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.2.0
> Reporter: Richard Stollar
> Priority: Minor
> Attachments: cxf-rt-transports-http.patch
>
>
> Then generating a web service client from WSDL the request sent to the server
> has an additional Content-Type header. Microsoft IIS 6.0 fails to process
> these requests and returns 200-OK with empty body.
> The Content-Type header should not be added to the http request when the
> method is GET.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
