Are you planning on implementing something for each of those phases? Spring’s Lifecycle contains start(), stop(), and isRunning(). JSF and Swing and I am sure many other things also have life cycles. We should implement the states we need because we need them, not to match some other technology.
Ralph On Sep 13, 2014, at 1:45 PM, Matt Sicker <[email protected]> wrote: > They're the most flexible. Quick overview of the life cycle in OSGi: > > installed -> resolved -> (starting) -> active -> (stopping) resolved -> > uninstalled > > Installed is the initial state. Resolved is when all its dependencies have > been fulfilled. During the starting state, if there is an error, then it goes > back to resolved. Active for while it's, well, active. Stopping puts the > thing back into resolved. Then, if you go from resolved to uninstalled, this > means that it's no longer available for use (and the only reason you'd find > something in this state for very long is due to a memory leak). > > Any objections? This would make our LifeCycle interface more compatible with > OSGi while providing a well-understood standard for the life cycle of > plugin-type objects. > > -- > Matt Sicker <[email protected]>
