You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "tli (JIRA)" <ji...@apache.org> on 2006/11/20 06:49:06 UTC
[jira] Resolved: (CXF-251) ReadHeadersInterceptor did not account
for whitespace before the closing header tag
[ http://issues.apache.org/jira/browse/CXF-251?page=all ]
tli resolved CXF-251.
---------------------
Fix Version/s: 2.0-M1
Resolution: Fixed
> ReadHeadersInterceptor did not account for whitespace before the closing header tag
> -----------------------------------------------------------------------------------
>
> Key: CXF-251
> URL: http://issues.apache.org/jira/browse/CXF-251
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.0-M1
> Reporter: Jonathan Hall
> Assigned To: tli
> Fix For: 2.0-M1
>
> Attachments: ReadHeadersInterceptorPatch.patch
>
>
> If headers where included in a SOAP request an error would occur saying Operation Body was not found. This was due to whitespace which did not create the expected outcome of passing over the body element.
> .nextTag() resolves this.
> However, apart from skipping whitespace .nextTag() also skips COMMENT, or PROCESSING_INSTRUCTION. If this is required then the following would also work.
> while (xmlReader.isWhiteSpace()) {
> xmlReader.next();
> }
> However, I don't believe there is support in place for processing COMMENT, or PROCESSING_INSTRUCTION when setting headers. So I used .nextTag()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira