[
https://issues.apache.org/jira/browse/TUSCANY-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910761#action_12910761
]
Scott Kurz commented on TUSCANY-3664:
-------------------------------------
Just wanted to note we need to keep in mind places in our code where we assume
that a Java method has an array of input args but only a single return value.
If the fix to implement full Holder support involves changing this assumption,
then we might need to reconsider some of these instances.
The example I have in mind is the binding.jms wireFormat.jmsObject support, in
which we have cases on the input side where we're concerned whether or not to
serialize an array or its contents. Not sure what other examples there might
be.
I haven't had time to look at your changes to see if you've consider this, but
just wanted to mention it while the JIRA was still open.
Scott
> Add holder support to 2.x
> -------------------------
>
> Key: TUSCANY-3664
> URL: https://issues.apache.org/jira/browse/TUSCANY-3664
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime, OASIS Compliance - TUSCANY
> Affects Versions: Java-SCA-2.0-M5
> Environment: All
> Reporter: Simon Laws
> Assignee: Brent Daniel
>
> There are a number of related JIRA that introduced some holder support and
> related samples to the 1.x code base including:
> TUSCANY-2332
> TUSCANY-2557
> TUSCANY-2768
> It's not clear whether the support added to 1.x was complete but it didn't
> apparently make it into 2.x which seems to be a bit of an oversight.
> We need to create some samples to exercise the various holder scenarios, OUT,
> IN/OUT etc. and then take a look at the 1.x changes to see if they are
> suitable for 2.x or whether we need to work up a different solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
