Simon Laws wrote:
Sebastien, it looks like a good start on the lazy loading to me.
On the disitributed runtime scenario point. I'd like to start putting the
distributed runtime bits I have so far into head so I would like to work
with you in making a start on the notion of a domain/runtime configured
through incremental changes. This could, in future, facilitate an event
driven runtime management function for the operations you mention. I
think
the first thing we could do is build an extension of the domain
implementation which supports the notion of the domain composite deployed
into the local runtime and make the exercise of building the domain
composite an exercise in adding those artifacts for which the runtime is
responsible. At the moment what I have is the domain composite being
created
after which the bits that the runtime is not responsible for are chopped
out.
Simon
+1 for doing all this work in trunk
This new SCA domain implementation will need to know which component
runs on which runtime, so I'll start adding some model interfaces to
represent that mapping and a description of the topology to the topology
module you created.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
