axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Godwin Chapman (JIRA)" <>
Subject [jira] Commented: (AXIS2-2399) Supporting plain old XML messages coming with a content type of text/xml
Date Tue, 27 Mar 2007 04:44:32 GMT


Keith Godwin Chapman commented on AXIS2-2399:

How can we achieve this with the messagebuilders concept? We map a particullar message builder
based on the contentType. The problem is that POX  services use text/xml as with SOAP 1.1.
Axis2 client cannot assume (as it can be incorrect to do so) that a SOAP 1.1 message will
have a SOAP action always. So how can we tackle this problem?

I tried writing a REST client for flickr and it did return text/xml all the time. I tackled
this problem by mapping text/xml to ApplicationXMLBuilder in my client axis2.xml.


> Supporting plain old XML messages coming with a content type of text/xml
> ------------------------------------------------------------------------
>                 Key: AXIS2-2399
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Thilina Gunarathne
>         Assigned To: Keith Godwin Chapman
>            Priority: Critical
> IIRC Axis2 used to support incoming POX messages with the content type text/xml.. Axis2
diffrentiated between POX and SOAP 1.1 based on the presence of SOAPAction header...
> I think this is a nice feature to have back, specially most of the POX services available
today sends you responses using text/xml... 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message