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]
