Thanks Toni.  I'm still around and I haven't given up the idea.  Hoping to
resurrect it soon.

On Fri, Jun 10, 2011 at 5:23 AM, Toni Menzel (JIRA) <j...@ops4j1.jira.com>wrote:

>
>     [
> https://ops4j1.jira.com/browse/TEC-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Toni Menzel closed TEC-14.
> --------------------------
>
>    Resolution: Fixed
>
> > Techne Launcher, Hot-Swapping OSGi Frameworks
> > ---------------------------------------------
> >
> >                 Key: TEC-14
> >                 URL: https://ops4j1.jira.com/browse/TEC-14
> >             Project: Techne
> >          Issue Type: New Feature
> >          Components: Techne.Launcher
> >         Environment: Java, Linux/UNIX, MacOS, Windows
> >            Reporter: Rick Litton
> >            Assignee: Toni Menzel
> >            Priority: Minor
> >
> > Toni Menzel wrote on 30 January 2007:
> > I got some pretty new and worthwhile ideas on the techne.launch
> component. Basically it is the component which is to be started with 'java
> -jar bin/techne.jar'. Currently this is bound to start the felix framework.
> But it is going to be extended to support equinox and kf in a seemless way.
> > Now, the question is: how and when does anyone select the framework to be
> used? The answer is: never, the launcher selects it using the context-driven
> approach. This is, the launcher looks whats available in it's environment
> (classpath,jars,fitting bundles) and starts what fits best. I think this
> could be packed into one component called techne.launch and can be used even
> outside techne by osgi folks.
> > Now, this is good but this one gets better: how about enabling
> framework-change on the fly? Ok, the simpliest approach would be just
> shutdown the whole framework (say Felix with all bundles) and relaunch the
> new framework with same state (which bundles to be started and so on).. say
> we switch from felix to equinox just by swapping jars in a directory.. (or
> even via ajax webconsole).
> > This could be continued to any extend: for example, the transitioning
> could be done in a more fluent way, so clients get minimal or no downtime.
>  How could this be done? mmhh.. how about having a host-framework (say
> Felix) as techne.launch. Other Frameworks just run on top of it as "bundle
> of the host environment". Transitioning now takes care that services if the
> hosted framework get minimal downtime..
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> _______________________________________________
> notify mailing list
> not...@lists.ops4j.org
> http://lists.ops4j.org/mailman/listinfo/notify
>
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to