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 for all the current
component types, we can get rid of the old ones.
That sounds radical but I tend to agree it's easiest way. It's about
splitting the current builder (which goes directly from logical model
to runtime component) into two parts: the logical->physical mapper
which we want to be able to run on the master, and the physical-
>runtime component builder which runs on the target runtime.
We could try to do that in place but I don't think would be very
incremental given we use the builders to bootstrap the system. I
agree it will be easier to have frameworks for the two parts and then
move the function from the current builder into them.
I have already started on the physical model. Since, this fits in
closely with the physical model and federated deployment, I can
include the new builder framwork in the work I am doing currently.
Cool :-) I'm happy to get stuck into the InstanceFactory stuff. I
think we'll need a common interface for these builders that they
implement and the FD calls. As a strawman, how about:
interface PhysicalComponentBuilder {
Component build(PhysicalComponentDefinition defn)
}
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
