component defintion to get the
component running on the slave. This gets marshalled and sent to
the slave through the discovery service. On the slave this is
picked up by the federated deployer to be umarshalled using the
marshaller framework. The component gets built from the physical
to be encapsulated in
the dynamically generated byte code for the instance factory. Maybe, Jeremy
has a view on this as well.
Ta
Meeraj
From: Jim Marino [EMAIL PROTECTED]
Reply-To: tuscany-dev@ws.apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Physical Component Defintion
Date: Thu, 8 Feb 2007 14:43
in the
dynamically generated byte code for the instance factory. Maybe,
Jeremy has a view on this as well.
Ta
Meeraj
From: Jim Marino [EMAIL PROTECTED]
Reply-To: tuscany-dev@ws.apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Physical Component Defintion
Date: Thu, 8 Feb 2007 14:43:40
@ws.apache.org
Subject: Re: Physical Component Defintion
Date: Thu, 8 Feb 2007 14:43:40 -0800
On Feb 7, 2007, at 2:49 PM, Meeraj Kunnumpurath wrote:
Jim,
I have been looking at the work you have been doing with
component manager and URIs and figuring out how this would fit
in with federated
From: Jeremy Boynes [EMAIL PROTECTED]
Reply-To: tuscany-dev@ws.apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Physical Component Defintion
Date: Thu, 8 Feb 2007 20:13:10 -0800
On Feb 8, 2007, at 4:42 PM, Jeremy Boynes wrote:
On Feb 8, 2007, at 3:26 PM, Meeraj Kunnumpurath wrote:
Also
Jim,
I have been looking at the work you have been doing with component manager
and URIs and figuring out how this would fit in with federated deployment
model I have been working on. Currently, the master creates the physical
component defintion to get the component running on the slave
