Thanks Edward for that nice breakdown of options!! :-)
On 2010-05-11 15.40, Edward Yakop wrote:
There are several level of compliance:
1. Simplest way (you discovered this):
All jars are library bundles, and there's only one bundle activator
and this one bootstrap the qi4j application.
Downside:
* Hard coding of the application layout in advance.
* Qi4j application is shutdown when any qi4j application related
bundle is down.
This is what I'm trying now. Seems simple enough.
2. Step 1 + Config admin + Layer / Module bootstraper as OSGi services
<snip>
Doesn't give enough benefit to be useful for me, I think.
3. Step 1 or 2 but split qi4j application to smaller application,
integrate between qi4j applications via OSGi services
Benefit:
* All step 1 or 2 benefits
* One sub application down does not mean down for the entire system.
You can partially upgrade qi4j application without shutting down
the entire system.
Downside:
* Increase complexity
What about the option where I have one activator that does the assembly,
using hardcoded layout, but 1 Module=1 bundle, and where the activator
listens for redeploy of those bundles, and tries to be clever in terms
of how much it restarts? E.g. redeploy bundle in Module for UI Layer ->
only UI layer restarts. Should be possible.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
