The headers element allows to directly specify a number of manifest headers.

The headers element takes one or more header elements. Each element takes a mandatory name attribute. The text value is provided as the element's content.

<bundle xmlns="http://www.jeremias-maerki.ch/ns/osgi-bundle">
  [..]
  <headers>
    <header name="Bundle-Activator">ch.jm.fop.osgi.Activator</header>
    <header name="Bundle-Vendor">Jeremias Märki</header>
    <header name="Service-Component">OSGI-INF/configurator.xml</header>
  </headers>
  [..]
</bundle>

The exports element allows to directly specify a number of packages to be exported.

The exports element takes one or more exportelements. The package name is provided as the element's content. To export a package including all subpackages, you may use a "*" as a wildcard.

Each export element takes an optional version attribute to override the version specified by the Bundle-Version header. If the version attribute is absent, each package export will have the bundle's version added as the exported version. All exported bundles will also automatically be imported with the same version number. This is in line with OSGi best practice.

<bundle xmlns="http://www.jeremias-maerki.ch/ns/osgi-bundle">
  [..]
  <exports>
    <export>org.apache.fop*</export>
    <!-- ...or ... -->
    <export>ch.jm.lpr</export>
    <export>ch.jm.lpr.client</export>
  </exports>
  [..]
</bundle>

The imports element allows to directly specify a number of packages to be imported. Normally, the bundle utility will automatically determine all required imports through byte code analysis but sometimes it's necessary to add directives or attributes to the import, for example, if you need optional resolution for some packages.

The imports element takes one or more import elements. The package name is provided in the required match attribute. To match multiple packages at one you may use "*" as a wildcard. The directives an attributes will then be applied to all these matching packages.

Normally, only imports that have been identified by byte code analysis are matched with the above mechanism. If you want to explicitely import a package, you can use the add attribute. The datatype here is xsd:boolean and the default is false for this attribute. The wildcard ("*") is not allowed if add="true".

<bundle xmlns="http://www.jeremias-maerki.ch/ns/osgi-bundle">
  [..]
  <imports>
    <import match="org.apache.tools.ant*">
      <directive name="resolution">optional</directive> 
    </import>
    <import match="com.acme.something" add="true">
      <attribute name="looney">true</attribute>
    </import
  </imports>
  [..]
</bundle>