[ https://jira.jboss.org/jira/browse/ISPN-193?page=com.atlassian.jira.plugi... ] Navin Surtani updated ISPN-193: ------------------------------- Summary: Provide a mechanism for the configuration XML parser to pass XML attributes to other modules for handling (was: Allow QueryInterceptor to be picked up from config.xml) Description: 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. was: Allow the QueryInterceptor within the query module to be picked up from the xml configuration. This way the temporary class QueryHelper will not be needed. Typically a user would specify infinispan.query.enabled = true in xml and from there the QueryInterceptor would be created and added onto the chain. -- 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

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

[ https://jira.jboss.org/jira/browse/ISPN-193?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic commented on ISPN-193: ------------------------------------------ So our requirements are: a) Configuration core module and its schema should stay the same b) The allowed exception to a) is to make some sort of generic extension point configuration element(s) c) Core module never knows anything or deals with configuration extension modules in b) d) Each non core module knows how to read its configuration extension and configure cache accordingly e) Each configuration extension is allowed to be a complex object graph, not a simple property (name/value) entry -- 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

[ https://jira.jboss.org/jira/browse/ISPN-193?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-193: ------------------------------------ Could be anywhere in theory, but as a practical example, the query module needs this. I think something like: <indexing enabled="true" indexLocalOnly="true" /> should be enough, and this would appear within the <namedCache ... /> element. -- 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