Hi Jordan! that is an interesting option, I kindly ask you to qualify the action associated to each phase/stage.
i.e., for configuration, we defined a dedicated `configuration`[1] module which, if used with `converters`[2], delegates to Guice the task to simply Inject & Configure elements; for validation, we also defined a dedicated module which integrates JSR303 (Bean Validation). We are anyway open to discuss in a rounded table other options, in order to simplify Onami components adoption by more users. TIA, all the best! -Simo [1] http://onami.incubator.apache.org/configuration/ [2] http://onami.incubator.apache.org/converters/ [3] http://onami.incubator.apache.org/validation/ http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Feb 25, 2013 at 2:36 AM, Jordan Zimmerman <jor...@jordanzimmerman.com> wrote: > What do you folks think about generalizing Lifecycle to support arbitrary > stages. Currently, there is AfterInjection and Dispose. Governator, for > example, has Pre Configuration, Configuration, Set Resources, Post > Construction, Validation and Warm Up. The "Disposer" interface could be > generalized into general purpose StageContainer and could manage state > changes on a object going through its lifecycle. Each stage would be > associated with an Annotation. > > Thoughts? > > -Jordan
