Raymond/Mike,
Thank you for your responses.
I like the idea that it is the responsibility of the binding provider to
ensure that data is correctly copied for cross-classloader calls. But will
that require the default binding.sca to be aware of classloaders? I will
have to look at the code in more
Raymond Feng wrote:
There is one more player: binding. The remote interaction is controlled
by the binding protocol. When the source and target components are
running under different context (such as classloader), the binding
provider should be responsible to make sure the data are correctly
Please see more comments below.
Thanks,
Raymond
--
From: "Rajini Sivaram" <[EMAIL PROTECTED]>
Sent: Monday, May 12, 2008 9:43 AM
To:
Subject: Re: SDO Databinding and classloaders
On 5/12/08, Raymond Feng <[EMAIL PROTECTED]>
-
> From: "Rajini Sivaram" <[EMAIL PROTECTED]>
> Sent: Sunday, May 11, 2008 1:44 PM
> To:
> Subject: SDO Databinding and classloaders
>
> Hello,
> >
> > I was looking at a JIRA related to SDO parameters to
.
Thanks,
Raymond
--
From: "Rajini Sivaram" <[EMAIL PROTECTED]>
Sent: Sunday, May 11, 2008 1:44 PM
To:
Subject: SDO Databinding and classloaders
Hello,
I was looking at a JIRA related to SDO parameters to OSGi services (
https://issues.apache.org/jira/browse/TUSCANY-2307), and
Hello,
I was looking at a JIRA related to SDO parameters to OSGi services (
https://issues.apache.org/jira/browse/TUSCANY-2307), and was not sure
whether the following scenario is valid for standard Java services in
Tuscany.
Component A and Component B are implemented using and
use default SCA b
