[SWS-579] AxiomSoapMessageFactory does not parse application/xop+xml Content-Type properly Created: 22/Oct/09  Updated: 04/May/12  Resolved: 10/Nov/09

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: 1.5.8
Fix Version/s: 1.5.9

Type: Bug Priority: Major
Reporter: Art O Cathain Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 13m
Original Estimate: Not Specified
Environment:

Weblogic 10.3



 Description   

AxiomSoapMessageFactory#getCharSetEncoding(), when given the following HTTP Content-Type header (which I assume is valid),

application/xop+xml;type="text/xml; charset=utf-8"

returns a CharSet of 'utf-8"' instead of 'utf-8' (i.e. there is an erroneous double quote at the end of the string).



 Comments   
Comment by Arjen Poutsma [ 10/Nov/09 ]

According to the HTTP spec, that Content-Type header would be incorrect (http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7). Which particular SOAP stack is creating that header?

At any rate, we we will fix it nonetheless.

Comment by Arjen Poutsma [ 10/Nov/09 ]

Fixed.

Comment by Art O Cathain [ 11/Nov/09 ]

Thanks for the fix. Both ends of the web service are running Spring-WS SOAP stacks.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Fri Dec 15 23:31:31 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.