[
https://issues.apache.org/jira/browse/TUSCANY-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612079#action_12612079
]
Jean-Sebastien Delfino commented on TUSCANY-2395:
-------------------------------------------------
I'll return the question to you, just look at the code, browse the
binding-ws-axis2 code and track what doesn't seem to be necessary in a default
SCA binding impl.
Or try to come up with an Axis2-based implementation of the default SCA binding
and then compare with the WS binding and see if you really needed everything
that's in there.
A few hints:
- soap 1.1 vs 1.2
- JMS support
- listing services and providing ?wsdl support
- mtom support
There's probably more...
> SCA default binding should not depend on the whole Web Service binding
> ----------------------------------------------------------------------
>
> Key: TUSCANY-2395
> URL: https://issues.apache.org/jira/browse/TUSCANY-2395
> Project: Tuscany
> Issue Type: Wish
> Components: Java SCA Core Runtime
> Reporter: Jean-Sebastien Delfino
> Fix For: Java-SCA-Next
>
>
> The SCA default binding is currently just wrapping the Web Service binding. I
> don't think that it's right as the Web Service binding is now starting to
> have to support more styles / variations than needed by the SCA default
> binding.
> IMO the SCA default binding should be a 'strict minimum' implementation of a
> SOAP WS-I basic profile doc-literal-wrapped binding, and not depend of the
> Web Service binding code, which will need to evolve to support many more
> styles.
> This will also allow people who are not interested in Web Services and do not
> want to install the richer Web Service binding to use a simpler / more
> lightweight binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
