Hello, it might be a anti-pattern for some. For others it is a anti-pattern to have a persistent (corruptable) state location required and used by the framework when the actual application bundles deliverable try to need no state, persistence and low permission.
The frameworks I have looked at (and Equinox is a particular unflexible example) make this hard for deployers. So deleting the directory (or starting with -clean) is not always an anti-pattern it is also a symptom for a unsatisfied need to trade startup speed against robustness. greetings Bernd -- http://bernd.eckenfels.net ----- Ursprüngliche Nachricht ----- Von: "[email protected]" <[email protected]> Gesendet: 13.08.2014 22:29 An: "OSGi Developer Mail List" <[email protected]> Betreff: Re: [osgi-dev] bundle.getDataFile(string) Marcel wrote: >> If you ask me, it definitely is. I know a lot of people kill the bundle >> cache on every startup and re-install all bundles each time, but I would >> advocate that that is bad practice in OSGi. Hear hear. In fact if there are anti-patterns out there then this is one of them - and not just because of getDataFile. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
