Agreed, except the extender pattern usually means examining installed bundles using the Bundle.getHeader() or Bundle.getEntry() methods. David talked about examining bundles *before* installation, which implies using the java.util.Jar API to read jars from the filesystem.
Neil On Wed, Jun 16, 2010 at 5:49 PM, Tommy M. McGuire <mcgu...@crsr.net> wrote: > On 06/16/2010 01:36 AM, David Conde wrote: >> Hi, >> >> What could I use in order to provide some custom information in the >> MANIFEST file in order to read this information before installing the >> bundle in Equinox? >> >> I mean, I would like to provide some extra information in the bundle but >> I would like to be able to read the information before installing the >> bundle so I thought to do it in the MANIFEST by using some special label >> if it exists. > > Adding MANIFEST.MF headers is pretty easy; the "read this information before > installing the bundle" part is harder. You are probably also going to want to > look at the extender pattern. Here's some random links: > > http://www.osgi.org/blog/2007/02/osgi-extender-model.html > http://www.aqute.biz/Snippets/Extender > > -- > Tommy M. McGuire > mcgu...@crsr.net > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
