[
https://issues.apache.org/jira/browse/TUSCANY-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Kurz updated TUSCANY-3894:
--------------------------------
Attachment: 3894.tests.patch
Some tests showing a couple of the issues I raised, e.g.
1) The fact that the copy works like binding.rmi in preserving referential
integrity, unlike binding.ws
2) The problem of doing a copy when different databindings are involved (see
testJSONSCA())
> 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.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
