[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tuscany-dev
Subject:    [jira] [Commented] (TUSCANY-3884) binding.sca local delegation
From:       "Scott Kurz (JIRA)" <dev () tuscany ! apache ! org>
Date:       2011-06-30 13:37:29
Message-ID: 1050951905.5474.1309441049942.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugi \
n.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057818#comment-13057818 ] \


Scott Kurz commented on TUSCANY-3884:
-------------------------------------

Simon,

Yes I realize I'm mixing up the issue of needing to delegate the local invocation \
with the question of how to do the data copy for a PBV local invocation. Sorry about \
that... I was responding to something I'd mention in my first comment asking for \
clarification, and then twisting that into an example of the need to delegate.

I might rephrase my comments as:
- today's PBV local invocation, in using Mediator.copyXXX, assumes that source/target \
                use the same databinding.
- use cases requiring different databindings would need a different copy algorithm, \
                e.g. using a WSDL operation and the Mediatory.mediateXXX methods
- assuming there's value in keeping the existing code (doing the copyXXX), we could \
factor these two different algorithms into two local delegate provider impls

That's where I was going, but one might also say that the PBV+local+copyXXX isn't \
really worth keeping after all, and should be replaced with a PBV+local+mediateXXX.   \
That is a separate issue, and I can open a new JIRA if it helps (I'm interested in \
understanding your comment: "I think that by this stage we know that the source and \
target are at least expected to be of the same databinding").






> binding.sca local delegation
> ----------------------------
> 
> Key: TUSCANY-3884
> URL: https://issues.apache.org/jira/browse/TUSCANY-3884
> Project: Tuscany
> Issue Type: Improvement
> Affects Versions: Java-SCA-2.0-Beta2
> Reporter: Simon Laws
> Priority: Minor
> Fix For: Java-SCA-2.0
> 
> 
> Binding.sca currently delegates for remote semantics but implements local semantics \
> in it's own provider. Should we create a separate local binding an delegate to that \
> so it can we swapped out without affecting the provider functionality. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]