rws / environment-api Goto Github PK

Currently AbstractLifeCycle provides list of methods(doInitLifeCycle, doStartLifeCycle, doPause, doResume, doStopLifeCycle) that can be used to define particular implementation of LifeCycle objects.
It also has functionality that handles state switching like changeState(State from, State to) in initLifeCycle(), startLifeCycle(), pause(), resume(), stopLifeCycle(). These methods are sensitive to current state, and incorrect overriding of one of these methods can simply brake functionality.

The solution might be making all these methods(changeState, initLifeCycle(), startLifeCycle(), pause(), resume(), stopLifeCycle()) final. Or we can introduce another class AbstractStatefulLifeCycle that will extend AbstractLifeCycle and where all state operation will be moved and declared there as final

It sometimes happens that we need to pass the provided Environment instance to another API usage or a library integration point as a Map or Properties encapsulation. The module should provide a new API to create an immutable instance of proper abstraction from an instance of Environment.

When using Environment API integrating with other libraries, they might require an external properties file to initialize. Currently, one cannot iterate over keys/values of an Environment instance and then write it to an external properties file. Either Environment should provide its keys as an API or a separate API should be introduced to allow I/O for an Environment.