You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2007/03/27 05:37:32 UTC
[jira] Created: (AXIS2-2399) Supporting plain old XML messages
coming with a content type of text/xml
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2399) Supporting plain old XML messages
coming with a content type of text/xml
Posted by "Keith Godwin Chapman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484301 ]
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.
Thanks,
Keith
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2399) Supporting plain old XML messages
coming with a content type of text/xml
Posted by "Keith Godwin Chapman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Godwin Chapman resolved AXIS2-2399.
-----------------------------------------
Resolution: Fixed
Fixed. If there is no soapAction in a request message treat it as application/xml. Introduce a property flag to set if we are doing SOAP response MEP. If the request if rest or the operation is SOAP response MEP treat the response as application/xml.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2399) Supporting plain old XML messages
coming with a content type of text/xml
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2399) Supporting plain old XML messages
coming with a content type of text/xml
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484453 ]
Davanum Srinivas commented on AXIS2-2399:
-----------------------------------------
If REST is enabled, then the soap related builders must be switched off somehow.
-- dims
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org