The issue is likely:
1. Some sort of conflict between the fragment and host.
2. The host is already resolved.
For (1), the Felix framework is sort of strict...I think some debug
messages might tell you if this happens. For (2), the spec doesn't
require dynamic attachment of fragments, so u
Fragment support in Felix always had its issues but i reacall it has
dramatically improved since 2.x releases. So yes, make sure to try later
felix versions, too.
It also heavily relates on that you do in your fragment MANIFESTs. (want to
share?)
Also watchout for felix error/warn messages as it so
Hello all,
As far as I know, felix supports fragments. At least as of version 1.8
Take a look at
http://opensource.luminis.net/svn/OSGITESTRESULTS/trunk/index.html.
The most recent frameworks support fragments (sec 3.14 in r4.1)
Felix 1.8.x is not listed but you can run the tests on your own
mach
If I'm not mistaken the fragment must be attached before the host is
started. So maybe it will help to put the fragment in the list before the
host.
Anyhow, I'm pretty much sure that is not an Pax runner issue. Try it also
with equinox for a try out.
My 2c.
On Fri, Nov 20, 2009 at 9:59 PM, Charl
Hello ppl,
I've setup a composite file with 3 scanbundle instructions. One of
them is a fragment, so I specify @nostart since a fragment cannot be
started. Now whenever I boot pax-runner, my fragment never gets
attached to the specified host bundle. The fragment-host manifest
entry is correct,
