[CXF-251] ReadHeadersInterceptor did not account for whitespace before the closing header tag

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-M1
• Fix Version/s: 2.0-M1
• Component/s: Soap Binding
• Assignee: Tom Li
• Reporter: Jonathan Hall
• Created: 17/Nov/06 13:26
• Updated: 29/Aug/07 02:06
• Resolved: 20/Nov/06 05:47

Description

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()