Leo Sutic wrote:
1. Marker interfaces ThreadSafe, SingleThreaded: How about doing a "soft" deprecation of them in the same way as we did for component manager et al?
sounds good.
2. Recomposable is (softly) deprecated with the text:We do have a contract for these interfaces (at http://avalon.apache.org/framework/reference-the-lifecycle.html, and codified in excalibur-utils ComponentStateValidator), even if underspecified. There is just not a container that makes use of them. Note that the Re* contract _is_ supported: the re*() methods are not guaranteed to be called, so they are simply not called :D
The Reconfigurable interface is a legacy interface with no concrete contracts.
Reconfigurable has no deprecation warning at all. Should we softly
deprecate
all Re* interfaces, like Reconfigurable and Recontextualizable?
The typo (reconfigurable instead of recomposable) should be fixed
anyway,
and I have done that.
I guess it has been shown in real life that most components managed by an avalon container are either inexpensive enough that it is a good option to just recreate them, or there is never a need to suspend long-running services, or some other mechanism is used for reconfiguring those.
The question that comes to mind is whether someone somewhere has indeed found a need for Re* and is using them. Dunno. How sure are we that there is no real-life use for the suspension concept?
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
