All,
(This email may be a dup for some of you... I forgot the [axis2] in the subject... oops. :) I recently ran into a bug where the ApplicationXMLBuilder was the preferred builder chosen by the TransportUtils.createDocumentElement, even though the needed builder was SOAP11Builder. The content-type "text/xml" in the http header is somewhat arbitrary in that the specs do not align it with REST vs. SOAP11. This seems to have caused quite a bit of back-and-forth change in the code that results in REST or SOAP11 being preferred over the other. To resolve this, I propose a configuration solution. An axis2 user may configure a "builderForTextXML" that would take precedence over the smart builder chooser logic in TransportUtils. This new configuration parameter would insure that servers that only support REST or SOAP11 for content-type "text/xml" would always use the right builder. Currently, the code will pick the ApplicationXMLBuilder on the client async response (see Jira for more detailed description of this). Please see jira with patch: https://issues.apache.org/jira/browse/AXIS2-3228 If there are no objections, I will be glad to commit this change. Mike Rheinheimer (512) 838-0086 t/l 678-0086 WebSphere WebService Core Engine Team
