Hey,
i want to use your implementation of the deployment admin service for my osgi
framework. I can start and get the service instance. But after calling the
method "installDeploymentPackage" i get always the exception, that no manifest
is present in the deployment package. I tested it, i can
As a user I really like the single bundle distribution that's currently
provided. And I feel a bit foolish as I have a hard time locating my http2
experiment workspace... in that workspace I created a single bundle
providing a ConnectorFactory and the additional Jetty dependencies that are
I think delivering a module that has no way to be used on its own, is
not very useful. If you always need at least the same 8 (or whatever
number) of bundles just to get a base functionality running, then why
are these 8 separate bundles? Especially as you have to use the same
version across
That sounds pretty interesting to me :)
Regards
Carsten
Am 22.10.2018 um 13:36 schrieb Bram Pouwelse:
As a user I really like the single bundle distribution that's currently
provided. And I feel a bit foolish as I have a hard time locating my http2
experiment workspace... in that workspace I
Dear Felix users;
The Felix team is pleased to announce the release of Dependency Manager R13
version. You will find a quick summary of the changes here:
http://felix.apache.org/documentation/subprojects/apache-felix-dependency-manager/guides/whatsnew-r13.html
This release is available from
I agree with Carsten, if we want to help the adoption of OSGI these kind of
bundles should be "plug 'n play" ;-)
It should also be simple to use another http service implementation (e.g.
glassfish) but this also is not very simple, there are also no tutorials
of any kind (that I know of) how to
6 matches
Mail list logo
