[
https://issues.apache.org/jira/browse/AXIS2-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484321
]
Thilina Gunarathne commented on AXIS2-2399:
-------------------------------------------
>How can we achieve this with the messagebuilders concept? We map a particullar
>message builder based on the contentType.
If there is an issue, we need to fix it some how :).. May be we can hack in
such a way that we can look at the correct combination & change the
content-type to application/xml somewhere before it reaches builder selector...
>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?
AFAIK SOAP Action is mandatory when sending a soap 1.1 request from a client
over HTTP..So the server side receiving will be fine... The issue will be with
receiving the response... We might have to remember what we send in order to
figure out what might be the response
>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.
We also ended up with the above (ugly?) fix..
> Supporting plain old XML messages coming with a content type of text/xml
> ------------------------------------------------------------------------
>
> Key: AXIS2-2399
> URL: https://issues.apache.org/jira/browse/AXIS2-2399
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
