[
https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590361#action_12590361
]
ant elder commented on TUSCANY-88:
----------------------------------
As a start we can support RPC-encoded by using XML components, but doing that
raises some issues:
- Axis2 no longer supports creating a ServiceClient from RPC-encoded WSDL
throwing an exception when it finds use="encoded". Could try to get that
changed in Axis2 as its only the Axis2 data bindings that should care.
- we've no facility to set the SOAP Action header other than from WSDL. Could
add a Tuscany specific attribute to binding.ws and/or support the jaxws
@Action attribute
- Tuscany script components no longer support WS references. Did work at one
point, i'd really like to be able to do (yes yes, i know inline scripts make
some people scowl):
<component name="TranslationComponent">
<tuscany:implementation.script language="js"><![CDATA[
function translate(from, to, text) {
var resp = translator.translate(
<tem:Translate xmlns:tem="http://tempuri.org/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
<lang xsi:type="xsd:string"> { from }_{ to } </lang>
<text xsi:type="xsd:string">"{ text } </text>
</tem:Translate>;
return resp..TranslateResult
}
]]></tuscany:implementation.script>
<reference name="translator">
<binding.ws
wsdlElement="http://tempuri.org/#wsdl.port(Translator/TranslatorSoap)" />
</reference>
</component>
> Support invoking simple RPC/encoded Web services
> ------------------------------------------------
>
> Key: TUSCANY-88
> URL: https://issues.apache.org/jira/browse/TUSCANY-88
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Reporter: ant elder
> Priority: Minor
> Fix For: Java-SCA-M2
>
>
> Currently externalServices using the WS binding don't support invoking RPC
> encoded services. To support RPC/encoded properly would be a lot of work and
> as its not WS-I compliant probably isn't a high priority, however as there
> are a lot of existing RPC/encoded services out there it would be good if we
> had some limitted support for the subset of RPC/encoded thats easy to do. It
> would great if at least it worked for trivial services like xmethods
> stockquote. Thats WS 101 and a lot of people will likely try using that when
> they first look at Tuscany. It would create a much better first impression if
> that works rather than giving the obscure exception you get if you try it
> today.
--
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]
