One thing that remains unclear - do we invoke lifecycle manager
interface if it is found specified on classpath even though module
extension is never used in configuration? My guess is that we need to
invoke lifecycle manager callbacks if and only if module extension is
actually specified in configuration. In that case we need to extend
LifecycleManager to have getModuleName() API signature.
On 09-11-05 6:52 AM, Manik Surtani wrote:
Well, it's hardly public API. It isn't even SPI, it's in
between an
internal interface and an SPI. :) so I'm not that concerned. No one
really should be using this interface except us.