[
https://issues.apache.org/jira/browse/TUSCANY-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571635#action_12571635
]
Raymond Feng commented on TUSCANY-1678:
---------------------------------------
The initial fix has been introduced by r628163. There are some discussions on
the ML about where/how the SPI should be added.
> Would like to improve performance by not doing a PBVInvoker.copy in a couple
> cases where it's unnecessary
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1678
> URL: https://issues.apache.org/jira/browse/TUSCANY-1678
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Data Binding Runtime
> Affects Versions: Java-SCA-1.0
> Reporter: Scott Kurz
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
>
> Copying an SDO, for example, can be expensive...
> The two cases I have in mind:
> A) The databinding framework has done a transform which has already resulted
> in a copy of the data.
> B) The binding impl does a copy of the data. (For example if the binding
> impl serializes/deserializes the data in order to cross JVMs)
> Perhaps a flag on the Message object could be used. One challenge to
> doing that would be the fact that the PBVInvoker is going to do the copy of
> the output before the output reaches
> the DataTransformationInteceptor.
> I don't know if there's a simple way around that. I can imagine moving the
> PBVInvoker after the DataTransformationInteceptor on the output path but at
> the expense of complication the whole
> Interceptor / invoker chain design.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
