[infinispan-dev] Module configuration proposal

[Vladimir Blagojevic]

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