[
https://jira.jboss.org/jira/browse/ISPN-193?page=com.atlassian.jira.plugi...
]
Manik Surtani commented on ISPN-193:
------------------------------------
This has nothing to do with queries in particular, its just that the query module needs
some config e.g., enabled (true/false), indexLocalOnly (true/false).
Right now these are passed in as system properties (yuck!)
ideally an end-user would have a <query /> tag in the config.xml
and this stuff could be parsed and added to the Configuration bean
but for the sake of extensibility I don't want this stuff to be in the core module
since each module could in theory require some configuration
and IMO that module should hold its own config bean
but the question of parsing comes about
Provide a mechanism for the configuration XML parser to pass XML
attributes to other modules for handling
---------------------------------------------------------------------------------------------------------
Key: ISPN-193
URL:
https://jira.jboss.org/jira/browse/ISPN-193
Project: Infinispan
Issue Type: Feature Request
Components: Querying
Reporter: Navin Surtani
Assignee: Navin Surtani
Fix For: 4.1.0.BETA1, 4.1.0.GA
The XML parser should be able to pick up configurations for other modules.
Typically a user could specify infinispan.query.enabled = true in xml and from there the
QueryInterceptor would be created and added onto the chain when the property is picked up
by the parser. If there is no intention to use the query module, this property should be
ignored.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira