Hi Shale, Did u raise a JIRA with effect to this? I guess I can have a look at this,
Thanks, Keith. On 6/24/07, shale <[EMAIL PROTECTED]> wrote:
I've written an axis service that a client is sending a content-type of text/xml to with his SOAP envelope. The Axis engine is changing the content-type to application/xml when it encounters text/xml. There are different message Builders defined for the two content-types. application/xml uses ApplicationXMLBuilder (by default), while text/xml uses SOAPBuilder. SOAPBuilder seems to parse the request just fine, but ApplicationXMLBuilder is adding an extra soapenv:Body tag which causes the parsing process to fail. Unfortuneately, even if I change the default builder for application/xml via th axis2.xml configuration file, the AxisConfigutator is overriding some of the content-type to builder mappings to specific builders (application/xml being one of them), so I'm right back to a Builder that doesn't work. Any suggestions? -- View this message in context: http://www.nabble.com/text-xml-to-application-xml-tf3970315.html#a11269637 Sent from the Axis - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
