Hi Martin,
Have you tried to package both subsystems A and B as children contents
of an "install" esa feature ?
This way seems that you won't need the OSGi repository (at least in
theory) and can install both using one single command.
regards,
Cristiano
On 23-06-2014 13:46, Martin Petzold wrote:
Dear OSGi developers,
I ran into some problem with the Apache Aries Subsystem
Implementation. The scenario is rather easy: lets take two subsystems
A and B (type feature). A has a requirement on a resource provided by
B. All resources are deployed as wrapped content resources within the
esa. We do not use any OSGi repository implementation. This is very
similar to Davids example on his blog [1], however, only one of the
subsystems would contain the shared bundle.
Why does the subsystem implementation throw a Resolution + Subsystem
Exception when I install A. Shouldn't it install A and just wait until
it is resolved at some point in time? This would be the corresponding
behaviour for a bundle within an OSGi framework.
Background: I would like to split up the target platform into separate
feature subsystems, e.g. core and test.
[1] http://coderthoughts.blogspot.de/2013/04/osgi-subsystems.html
Thanks and best regards,
Martin
_______________________________________________
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
