[infinispan-dev] Module configuration proposal

[Manik Surtani]

Essentially, modules are internal constructs that we use to make the  
codebase more manageable. End users shouldn't need to know or care  
whether a feature is in a separate module or not. To some degree the  
end user is aware of some separation (different jars to add) but that  
should be the extent of exposure. :)

That is the ideal setup of course.

Sent from my iPhone

On 6 Nov 2009, at 14:58, Manik Surtani <manik at jboss.org> wrote:

> <infinispan>
> <namedCache name="blah">
> <indexing enabled="true" localOnly="false" />
> </>
> </>
>
> Sent from my iPhone
>
> On 6 Nov 2009, at 14:18, Vladimir Blagojevic <vblagoje at redhat.com>
> wrote:
>
>> On 09-11-06 6:37 AM, Manik Surtani wrote:
>>> A couple of comments re 193:
>>>
>>> How would you set this stuff programmatically? Conf.setQueryConfig
>>> (qc) ?
>>>
>>> Also, are the<module>  tags and the<query:>  prefix necessary in the
>>> XML config? Any clever way to do without these, since the  
>>> queryconfig
>>> bean is detected at the beginning and doesn't have to be loaded when
>>> specific tags are encountered, right?
>>>
>>> Cheers
>>> Manik
>>>
>> We can make it programmatic, no problem.
>>
>> Prefix, we have to keep since JAXB forces it. We can avoid its usage
>> if we manually change generated schema.
>>
>> How would you ideally align these tags?
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev