[
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
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: Vladimir Blagojevic
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