[infinispan-dev] Module configuration proposal

[Manik Surtani]

Well, even if the module extension is in the cfg XML file, core doesn't know how to parse it and it may be disabled.  

IMO the lifecycle callbacks should happen anyway.  It is up to the lifecycle implementor to decide whether to do anything or just be a no-op (if not enabled, etc).


----- Original Message -----
From: "Vladimir Blagojevic" <vblagoje at redhat.com>
To: infinispan-dev at lists.jboss.org
Sent: Saturday, 7 November, 2009 17:10:16 GMT +00:00 GMT Britain, Ireland, Portugal
Subject: Re: [infinispan-dev] Module configuration proposal

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.
>
>    

_______________________________________________
infinispan-dev mailing list
infinispan-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev