Hmmm. DS is really intended to deal with intra-bundle dependencies, although there's really no reason it could be applied like you describe.
In the DS spec, you would make the coupling explict by declaring component B depended on component A. For OSGi, it's more of a coping mechanism because the situation you describe kept arising. There's no magic, really. OSGi also has a start-level concept that applies to bundles (sort of the coarse-grained composites), and of course the bundle dependencies that can be specified in the OSGi Manifest - people have tried to use these to control these sorts of implicit dependencies with limited success. For me, I prefer just coming out as stating them. Honesty is the best policy? :-) -----Original Message----- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: Friday, July 14, 2006 4:50 PM To: [email protected] Subject: Re: Component start order Joel, forgive me if I missed it but if I have two "Immediate" components in the same bundle with no dependencies (so they are implicitly "Satisfied") , is there anything that determines in which order they start? The (awkward) scenario I have in mind is where there is no explicit dependency between components but there is some implicit coupling that implies an order. For example, they both call some common component and it needs to be called in the right order. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
