Basically the runtime has two hierarchical trees, one for application
composites and one for system composites. They are "separate" but
contained by the runtime. The bootstrapper will be responsible for
setting all of this up, including default system composites and
services so end-users won't need to mess with this. Jeremy's been
working on that part I believe on his trip now so hopefully he'll
have something to show us soon :-)
Jim
On Jun 25, 2006, at 5:54 PM, Rick wrote:
Just a question on this ... today the code creates a "parent"
CompositeComponentImpl. Would this eventually be replaced by the
Tuscany loaded system being the parent that is read in from system
SCDL ? Or would these component trees be kept separate?
Still trying to see how all the pieces fit, but I have to say this
really helps.
Jim Marino wrote:
ok cool - I'm going to bed ;-)
On Jun 25, 2006, at 2:12 PM, Jeremy Boynes wrote:
I did a couple of tweaks to this in r417080 to start using the
capabilities of the deployer. It's not quite done but I wanted to
commit what I had (during a layover in ORD) as I think it will be
easier to understand than the bare mechanics in Jim's example.
For now I turned it into a system component so that I could use the
primordial deployer - that should not have much of an example as the
two containers are so close. I will switch this back once we have a
default system configuration.
Jim, as a heads up I'm going to tweak the composite startup code so
that we don't need to leak the scope container to the deployer's
client. I hope to get that done on the next leg :-)
--
Jeremy
On 6/24/06, Jim Marino <[EMAIL PROTECTED]> wrote:
I've add a simple temporary class that to the eagerinit sample -
LifecycleDemonstration - that demonstrates component lifecycle
management, eager initialization, and destruction. As soon as we
get
the SCDL loading connected to the builders, this class can go away
and we will be able to demo an end-to-end scenario. In the
meantime,
I thought this would be helpful to show the relationship between
atomic components, scope containers, and composites.
Jim
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
