On Feb 3, 2007, at 1:01 PM, Meeraj Kunnumpurath wrote:
6. What I would suggest is to start a new builder framework in
parallel and deprecate the old one. The current deployer can
continue to use the old builder framework and the federted one will
use the new one. Once we have the builders fo
On Feb 3, 2007, at 1:01 PM, Meeraj Kunnumpurath wrote:
Jeremy,
I have been working on the marshallers for the physical model, so
that they can be transported from master to slave runtimes in a
federated model. I think what you suggested is closely related to
what I am working on. If I un
ache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
Date: Sat, 3 Feb 2007 12:38:38 -0800
On Jan 29, 2007, at 6:50 PM, Jeremy Boynes wrote:
Instead, I think the data sent should define the configuration data
ne
The basic change here would be to define an InstanceFactory that
returns a fully initialized instance for the target component:
class InstanceFactory {
InstanceWrapper createInstance();
}
The implementation of this can be provided by the user (which
allows codegen at development time), ge
On Jan 29, 2007, at 6:50 PM, Jeremy Boynes wrote:
Instead, I think the data sent should define the configuration data
needed by the JavaComponentBuilder, something like:
http://tuscany.apache.org/xmlns/java/
1.0"
uri="http://www.example.com/D1/Component1";
On Jan 30, 2007, at 1:32 PM, Raymond Feng wrote:
Hi, Jeremy.
Thank you for the explanation.
One more thing to clarify:
Assuming I have a folder structure on the file system to host my
contribution:
/tuscany/apps/MyApp/
/tuscany/apps/MyApp/META-INF/sca/default.scdl
/tuscany/apps/MyApp/xsd/
would assume once the component definitions are built we can use the
existing buildres.
Ta
Meeraj
From: Jeremy Boynes <[EMAIL PROTECTED]>
Reply-To: tuscany-dev@ws.apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
ymond
- Original Message -
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, January 30, 2007 12:13 PM
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
On Jan 30, 2007, at 11:40 AM, Raymond Feng wrote:
Yes. The JAR
On Jan 30, 2007, at 11:40 AM, Raymond Feng wrote:
Yes. The JAR is a packaging format understood by a
ContributionService in the domain. Based on the media type
(application/zip or application/x.tuscany.jar) this is processed
by the appropriate ContributionProcessor implementation and the
Hi,
I have more questions below.
Thanks,
Raymond
- Original Message -
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To:
Sent: Monday, January 29, 2007 6:50 PM
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
On Jan 29, 2007, at 5:20
Jeremy,
Pls see questions below.
Thanks
Meeraj
From: Jeremy Boynes <[EMAIL PROTECTED]>
Reply-To: tuscany-dev@ws.apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
Date: Mon, 29 Jan 2007 18:50:36 -0800
On Jan 29
On Jan 29, 2007, at 5:20 PM, Raymond Feng wrote:
Hi,
I think it's better to discuss the design in the context of a
simple scenario so that we can see the whole picture. I'm giving a
try to capture what I understand. Please forgive me if there's
anything dumb and help me complete/fix it.
age -
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To:
Sent: Monday, January 29, 2007 4:17 PM
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
On Jan 29, 2007, at 3:47 PM, Meeraj Kunnumpurath wrote:
Based on the third option, I think w
From: Jeremy Boynes <[EMAIL PROTECTED]>
Reply-To: tuscany-dev@ws.apache.org
To: tuscany-dev@ws.apache.org
Subject: Re: Federated Deployment (was SCDL Location in Composite
Implementation)
Date: Mon, 29 Jan 2007 16:17:21 -0800
On Jan 29, 2007, at 3:47 PM, Meeraj Kunnumpurath wrote:
On Jan 29, 2007, at 3:47 PM, Meeraj Kunnumpurath wrote:
Based on the third option, I think we need to come up with the
following,
1. Classes that represent the physical model that represents the
artifacts sent to target slave runtimes for deployment.
2. A component that is responsible on th
org
To: tuscany-dev@ws.apache.org
Subject: Re: SCDL Location in Composite Implementation
Date: Mon, 29 Jan 2007 15:24:56 -0800
The normative reference here is the name of the composite being used -
scdlLocation and scdlResource are things we've added to allow that name to
be resolved in a Java run
The normative reference here is the name of the composite being used
- scdlLocation and scdlResource are things we've added to allow that
name to be resolved in a Java runtime as, to date, there is no spec-
defined mechanism for doing that. This is related to the artifact
resolution thread R
Hi,
Currently SCDL location is modelled as a URL in CompositeImplementation
class. This works ok as long as the SCDL is loaded from a URL. However, with
the stuff I am working on with federated assembly, an SCDL may be
transported into the runtime through the discovery mechanism and thw SCDL
18 matches
Mail list logo
