I think that one didn't make it in time to be considered.
Now that the OASIS code was changed to pass the
SCAClientFactory.newInstance properties on to the impl we might be
able to add a Tuscany specific property to support that. Eg something
like:
Properties p = new Properties();
p.addProperty("allowsPassByReference", "true");
SCAClientFactory.newInstance(p, domainURI).getService(...);
...ant
On Mon, Jul 18, 2011 at 5:07 PM, Raymond Feng <enjoyj...@gmail.com> wrote:
> Mike, can I raise another issue?
> For the following API:
> org.oasisopen.sca.client.SCAClientFactory.getService(Class<T>, String)
> Can we add an option for "allowsPassByReference"? The latest SCA spec
> requires that both reference and service impl to allow pass-by-reference to
> avoid copying data over remotable interfaces. Without an option for the
> client API, we always need to pay the penalty.
> Thanks,
> Raymond
> ________________________________________________________________
> Raymond Feng
> rf...@apache.org
> Apache Tuscany PMC member and committer: tuscany.apache.org
> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
> Personal Web Site: www.enjoyjava.com
> ________________________________________________________________
> On Jul 18, 2011, at 3:55 AM, Mike Edwards wrote:
>
> Folks,
>
> An OASIS Java TC issue has been raised for these problems:
>
> http://www.osoa.org/jira/browse/JAVA-243
>
> along with the proposed updates, which can be seen in Section B.1.3 of this
> updated spec:
>
>
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/42910/sca-javacaa-1.1-spec-wd052.pdf
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/42909/sca-javacaa-1.1-spec-wd052.doc
>
>
> Yours, Mike.
>
>
