|
|
|
Re: Dependent Applications [message #868769 is a reply to message #868757] |
Wed, 02 May 2012 14:12 |
|
Well, what did you use with your Equinox based runtime?
Off the top of my head ... you can probably use DS or Blueprint to control the service dependencies but I'm not sure this will fit your use-case.
|
|
|
|
|
Re: Dependent Applications [message #869462 is a reply to message #868873] |
Thu, 03 May 2012 12:43 |
|
Hi Johan,
What you can do to control the startup order is to use:
- plans
- DS, Blueprint or similar framework
Plans can be embedded in other plans so combining this neat feature with initialArtifact you can start first your framework application and then ensure your add-ons are started in a certain order if this is really needed.
Personally I prefer frameworks such as DS and Blueprint to ensure that the components are functional only when their dependencies (services, configuration) are provisioned. The start order then should not really matter (except for the parent/framework app) since once all dependencies are satisfied the framework will take care to activate your add-on. This works well for smaller projects but I have no idea if this is applicable for your project structure as well.
|
|
|
|
Powered by
FUDForum. Page generated in 0.04723 seconds