[
https://issues.apache.org/jira/browse/TUSCANY-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Kurz updated TUSCANY-3894:
--------------------------------
Attachment: 3894.patch
Here is a patch which only does the copy in the binding if it detects that the
DataTransformationInterceptor will NOT be established on the wire.
It may leave some things to be desired...
For one, what if the Mediator-invoked transformer(s) somehow don't result in a
copy being made (is this even possible?) Then we wouldn't get the PBV
semantics. That said, I can't think of such a case today for existing
transformers. Also note that BaseDataBinding.copy just returns its input (i.e.
does NOT do a copy), so we could have such a hole in theory..but probably not
in practice..today.
Also, it might be nicer to do the "isPBV" and "isTransformationRequired" in a
single place, or somehow unify the two calculations so we don't have to call
"isTransformationRequired" twice, but I can't think of a better way right now.
Finally, I know we've been trying to be careful about declaring cross-module
SPIs wrt the OSGi runtime, so not sure if anyone would object to now exporting
a new package:
org.apache.tuscany.sca.core.databinding.wire
> Binding.sca local behavior: copy vs. mediate, same-databinding assumption
> --------------------------------------------------------------------------
>
> Key: TUSCANY-3894
> URL: https://issues.apache.org/jira/browse/TUSCANY-3894
> Project: Tuscany
> Issue Type: Improvement
> Components: SCA Java Runtime
> Affects Versions: Java-SCA-2.x
> Reporter: Scott Kurz
> Assignee: Scott Kurz
> Priority: Minor
> Fix For: Java-SCA-2.0
>
> Attachments: 3894.patch, 3894.tests.patch
>
>
> As discussed in: https://issues.apache.org/jira/browse/TUSCANY-3884
> the binding-sca-runtime code seems to assume that the reference/service sides
> share a common databinding, which might not be a desirable limitation.
> Also the object reference graph of copy vs. mediate seems to be different,
> which might not be preferable either.
> Just working on some tests now before commenting further, however I wanted to
> open this up to move the discussion out of the 3884 JIRA, to avoid confusion
> as this is a separate issue from simply adding the ability to delegate.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
