[infinispan-dev] Module configuration proposal

[Manik Surtani]

Hmm, I don't know.  The whole purpose behind this was to simplify our inter-module dependencies on config beans, etc.  And if simplifying means pushing more complexity on to the end user, then that's not good.  I'd rather have inter-dependencies and complexity in our codebase and a simple end-user experience than the other way around.

I suppose the alternative is that every time a module requires some cfg params, we modify the Configuration bean in core to accommodate this.  So this will add *some* knowledge of the modules in core (only from a configuration perspective) but at least it would keep the end-user experience clean.  So in the case of querying, something like:

Configuration.setIndexingEnabled(), Configuration.setIndexLocalOnly() and this would give us a config file that looks like the following?

<infinispan>
  <namedCache name="blah">
    <indexing enabled="true" localOnly="false" />
  </>
</>

If that is the case then this would mean we don't bother with ISPN-193 - sorry, I know you did put effort into investigating this :( - but we would still need ISPN-245.

Thoughts?

Cheers
Manik


----- Original Message -----
From: "Vladimir Blagojevic" <vblagoje at redhat.com>
To: "infinispan -Dev List" <infinispan-dev at lists.jboss.org>
Sent: Sunday, 8 November, 2009 20:29:27 GMT +00:00 GMT Britain, Ireland, Portugal
Subject: Re: [infinispan-dev] Module configuration proposal

I do understand that sentiment - not wanting to overwhelm end user with 
complex configuration file. How about we make a trade off. Module 
develop can specify default configuration bean setup in module.cfg (XML 
format), end user just references that module in cache.xml. End user, of 
course, has an option to change or overrride configuration in that 
module.cfg file package by either modifying it inside module jar or by 
specifying configuration directly in cache.xml as we have it now.

<infinispan>
<namedCache name="blah">
<modules>
<module name="query"/>
</modules>
</>
</>




On 09-11-08 11:04 AM, Manik Surtani wrote:
> Hmm - lets have a think about this.  Can't say I like having the<module>  tag exposed to end users.
>
> So I guess the alternative is to have module-specific config beans in the core module?  E.g., move the QueryConfiguration to the core package, and then we could have something like the following?
>
>    
>> <infinispan>
>> <namedCache name="blah">
>> <indexing enabled="true" localOnly="false" />
>> </>
>> </>
>>      
> Cheers
> Manik
>
>    

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