Hi Charlie,
if you mean boot features, you can use stage with ( ... ).
For "regular" features, you have to use features requirement.
If your features uses xmlns 1.3.0, you can add a requirement to the
datasource service, and then the other feature can require the
datasource service.
Regards
JB
On 07/05/2015 05:26 PM, Charlie Mordant wrote:
Hi Karaf experts!
Is there a way to force feature ordering in K4? It was obvious with K3,
but I didn't succeed to mimic it. I tried requirement/capability or
prerequisite="true", but it does not seem to work.
Here's the concrete use case:
I must have <pax-jdbc-config> + <myDsDriver> installed first, then a
config file (the <datasource-definition>), then the openjpa JPA feature
and finally my integration test.
I tried something like this without success (in pseudo xml):
<feature "myItest">
<feature "myDs"/>
<feature "openjpa"/>
<bundle "myTestJar"/>
</feature>
<feature "myDs">
<feature "myDsDriver"/>
<config "myDsConfig"/>
</feature>
<feature "myDsDriver">
<bundle "derby"/>
<feature "pax-jdbc-config"/>
</feature>
Regards,
Charlie
--
Charlie Mordant
Full OSGI/EE stack made with Karaf:
https://github.com/OsgiliathEnterprise/net.osgiliath.parent
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
