On Mon, Jun 10, 2013 at 4:32 PM, Ravi Undupitiya <[email protected]> wrote:
> I managed to fix this by adding the following to axis2.xml: > > <messageFormatter contentType="application/rdf+xml" > > class="org.apache.axis2.transport.http.ApplicationXMLFormatter"/> > > <messageBuilder contentType="application/rdf+xml" > > class="org.apache.axis2.builder.ApplicationXMLBuilder"/> > > I think this is the right way around this since RDF is XML. > > But this scenario works in HTTP-NIO transport without having to explicitly > define the content type. > > Any advice on the proposed solution? > If you set a debug point in MessageProcessorSelector class you can easily find how it returns the correct Message Builder/Message Formatter on NHTTP. But the accurate and guaranteed approach[1] is define Message Builder/Message Formatter with their content types on axis2.xml like you have done above. [1] - http://wso2.org/library/articles/axis2-configuration-part2-learning-axis2-xml#mb Thanks ! > > > > Thanks, > Ravi > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
