Reply inline. On Tue, May 11, 2010 at 15:52, Rickard Öberg <[email protected]> wrote: >> 2. Step 1 + Config admin + Layer / Module bootstraper as OSGi services > > <snip> > > Doesn't give enough benefit to be useful for me, I think. Probably, but if you combine step 1 + Config admin You can have "cloud" feature, where 1 set of application bundles, persistent configuration (for example) configured via config admin.
>> 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. Agree, As Marcel said, it shouldn't be too hard, just use BundleTracker and you're good to go. The only trouble with UI layer for example, the session might be lost, if it's not loss, we need to be careful about de-serializing user session (classes might no longer be there). It could be painless or painful :) Regards, Edward Yakop _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
