Hi,
I'm working in a tool that generates subsystem archives and have some
doubts.
The spec states that:
A Subsystem is deployed as a Subsystem Archive (.esa) file. Subsystem
Archives are used to store
Subsystems and optionally their resources in a standard ZIP-based file
format. This format is defined
in [4] Zip File Format. Subsystems normally use the Subsystem Archive
extension of .esa but are not
required to. However there is a special MIME type reserved for OSGi
Subsystems that can be used to
distinguish Subsystems from normal ZIP files. This MIME type is:
application/vnd.osgi.subsystem
But I'm not sure if the mimetype entry *must* be in the archive file.
If it were not mandatory, implementations will be free to use the entry
file name (and extension) to distinguish valid contents... and that
could be problematic...
Another doubt...
A Subsystem is a ZIP file that:
Contains zero or more resources. These resources may be OSGi bundles
or other Subsystems.
Subsystems may be nested or included to any depth.
Contains an optional Subsystem Manifest named OSGI-INF/SUBSYSTEM.MF.
The Subsystem
Manifest describes the contents of the Subsystem Archive and provides
information about the
Subsystem. The Subsystem Archive uses headers to specify information
that the Subsystems im-
plementation needs to install, resolve and start the Subsystem
correctly. For example, it can state
the list of content resources that comprise the Subsystem and the
Subsystem's type.
Contains an optional Deployment Manifest file named
OSGI-INF/DEPLOYMENT.MF. The Deploy-
ment Manifest describes the content resources, dependencies, and
sharing policy that need to be
provisioned to satisfy the Subsystem definition and ultimately allow
it to resolve at runtime.
What is mandatory in a subsystem archive? if both Subsystem Manifest and
Deployment Manifest are optional what info should a implementation use
to create and register the subsystem service from an archive?
many thanks,
Cristiano
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
