[
https://issues.apache.org/jira/browse/AXIS2-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-311:
-----------------------------------
Assignee: Sanka Samaranayake
> add SOAP Response SOAP MEP support
> ----------------------------------
>
> Key: AXIS2-311
> URL: https://issues.apache.org/jira/browse/AXIS2-311
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: transports
> Reporter: Sanjiva Weerawarana
> Assigned To: Sanka Samaranayake
> Priority: Minor
>
> SOAP 1.2 defines a *SOAP MEP* called SOAP Response. See:
> http://www.w3.org/TR/2002/WD-soap12-part2-20020626/#soapresmep.
> NOTE: SOAP MEPs are different from WSDL MEPs .. and Axis2's concept of MEP is
> a WSDL 2.0 MEP, not a SOAP MEP!
> SOAP Response is basically a way to do be able to do a regular HTTP GET and
> have the response be a SOAP envelope yet for the whole exchange to appear as
> a SOAP exchange as far as the client is concered. Glen should be able to give
> us more info on the subtleties .. this was a particularly sensitive topic in
> the SOAP 1.2 group as it was viewed as a way to bridge between the WS world
> and the REST world.
> With the recently committed HTTP POST/GET capability for IRI-styled
> operations (see WSDL 2.0 for this terminology), we should be able to do this
> quite trivially.
--
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]
