[
https://issues.apache.org/jira/browse/TUSCANY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620330#action_12620330
]
Wojtek Janiszewski commented on TUSCANY-2469:
---------------------------------------------
What do you think about current status of this module? What I think is missing
are more JUnit tests. Any ideas?
I'm also wondering if it's somehow possible to use SDO as an exception - now
any SDO cannot be used, SDO and JAXB cannot be mixed together. Any thoughts?
> Lightweight implementation of the SCA default binding over the corba binding
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-2469
> URL: https://issues.apache.org/jira/browse/TUSCANY-2469
> Project: Tuscany
> Issue Type: Wish
> Components: Java SCA Misc Binding Extensions
> Reporter: Jean-Sebastien Delfino
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
> Attachments: sca-binding-corba-jira-2469-21-july.patch,
> sca-binding-sdo-problem-jira-2469-30-july.patch
>
>
> I'd like to have an implementation of the SCA default binding over the corba
> binding, as a lightweight alternate to the current SOAP/Axis2 based
> implementation.
> This implementation should be as transparent to the application developer and
> assembler as the current default binding implementation (i.e. not impose
> special constraints on the service interfaces, or additional codegen or
> deployment or admin steps). We should also make sure that it is able to flow
> instances of our main data bindings (including JaxB and SDO).
> Having that would also allow us to verify that the current SCA binding is
> easily pluggable / replaceable by others who decide to integrate Tuscany but
> want to use a different prototol than SOAP inside their SCA domain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
