Gee, JIRA bug please.
thanks, dims On 3/26/07, Gee Chia <[EMAIL PROTECTED]> wrote:
Hi, All: I am writing to report a potential problem about content type for a response message using SOAP 1.2. Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem. HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8 Transfer-Encoding: chunked As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType, (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";;), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;". I am using Axis2 daily build of early of early March. If you have any advice about the problem, I appreciate a lot. Regards, Gee Chia Emerging Standards Development [EMAIL PROTECTED]
-- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
