You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2011/06/24 12:06:47 UTC
[jira] [Created] (TUSCANY-3884) binding.sca local delegation
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
[jira] [Commented] (TUSCANY-3884) binding.sca local delegation
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057715#comment-13057715 ]
Simon Laws commented on TUSCANY-3884:
-------------------------------------
Yes. Maybe semantics wasn't the right word to use. I'm referring to the code that does local invocation (both PBV and PBR) being separate from the code that does remote invocation. This is true at the moment it's just that the local block of code is no modularized in the same way that the remote block of code is.
Re. copy. We maybe need a separate JIRA for that but just for the moment...
For PBR IIRC the local binding optimization applies a databinding on the reference side and misses out the databinding on the service side hence when reference and service interfaces are different the appropriate databinding is applies.
For PBV there is the extra line that "copies" the result of the client side databinding. I think that by this stage we know that the source and target are at least expected to be of the same databinding. That might not be JAXB though. Is that what you were getting at?
> 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
[jira] [Closed] (TUSCANY-3884) binding.sca local delegation
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws closed TUSCANY-3884.
-------------------------------
Resolution: Fixed
Change committed at r114511 to make the local invocation a delegation in a similar way to remote invocation.
> 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
> Assignee: 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
[jira] [Commented] (TUSCANY-3884) binding.sca local delegation
Posted by "Scott Kurz (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057469#comment-13057469 ]
Scott Kurz commented on TUSCANY-3884:
-------------------------------------
I just realized a more fundamental issue with using copyXXX is that it assumes both source and target use the same databinding. At least, the JAXBDataBinding.copy() assumes both source and target are JAXB.
So one thing I can see a need for in a delegate impl is the usage of a WSDL operation to model the binding operation and the use of mediateXXX to transform.
> 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
[jira] [Commented] (TUSCANY-3884) binding.sca local delegation
Posted by "Scott Kurz (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugin.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
[jira] [Commented] (TUSCANY-3884) binding.sca local delegation
Posted by "Scott Kurz (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054524#comment-13054524 ]
Scott Kurz commented on TUSCANY-3884:
-------------------------------------
Simon,
You're talking about local as in colocated (single JVM), right? Not local as in PBR, in contrast to remotable (PBV). Just clarifying since most times I've seen the word "semantics" we're talking about PBR vs. PBV.
I'm not just nitpicking since there are some data-related semantics associated with the current colocated code. By this I'm referring to the use of Mediator.copyXXX rather than the use of the mediateXXX methods invoked by the DataTransformationInterceptor. The copy results in a different object graph than the DTI and also I believe does not use wrapper->wrapper transform whereas the DTI typically does in our default Java/JAXB use case.
But I think you're mostly referring to delegating to the provider impl like we do with the non-colocated (distributable) case?
> 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
[jira] [Assigned] (TUSCANY-3884) binding.sca local delegation
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws reassigned TUSCANY-3884:
-----------------------------------
Assignee: Simon Laws
> 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
> Assignee: 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