Hi, > On 10 Nov 2016, at 13:27, [email protected] wrote: > > In some cases I have a requirement that a bundle should not resolve (or > start) when a certain external 'thing' hasn't taken place yet. For example > maybe you may not want to start a certain bundle until some operations have > been performed on a database.
I’m not sure I understand the rationale for making the bundle non-resolvable when you want to wait for a certain (service?) operation to be complete. If you’re talking about database migrations that need to be performed before the services of your bundle are exposed to the rest of the system, then you could also prevent them from being registered until the migration scripts are finished. For a project of ours, we’ve implemented this pattern for all of our database migrations and it works really well. For this, we used a custom on/off service-dependency (we’re using DM4 for that) for our services that we could flip once the migration was complete causing DM to actually register the services. -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 My world is something with Amdatu and Apache Luminis Technologies Churchillplein 1 7314 BZ Apeldoorn +31 88 586 46 00 https://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8170.94.441.B.01
signature.asc
Description: Message signed with OpenPGP using GPGMail
