On 30.08.2011 12:51, Ivanhoe Abrahams wrote:
> I noticed that it really depends on the start order of the bundles whether
> my simple class gets woven or not.
This is because you haven't really declared any kind of logical dependency
between the bundles; if your client bundle can work without weaver, the
framework will happily start it - and why wouldn't it?
Using a start order is a manual way to "fix" this, but due to its global
nature (global meaning it only makes sense when considered across all
bundles, which therefore must be known up front!) start order in general
is fragile and not recommended.
> I was wondering what the best way would be to ensure that my bundle
> containing my weavinghook gets started first?
> Is assigning a startlevel the only way that I can achieve this?
I think going forward from 4.3+ we will increasingly see use of
requirements & capabilities matching, esp. when the new OBR spec is
released and implemented ("real soon now" :). This will enable much more
flexible modeling of dependencies between interacting entities than static
ordering.
-h
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
