[
https://issues.apache.org/jira/browse/CHAIN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedikt Ritter updated CHAIN-16:
---------------------------------
Summary: Suggested enhancement for ChainListener (was: [chain] Suggested
enhancement for ChainListener)
> Suggested enhancement for ChainListener
> ---------------------------------------
>
> Key: CHAIN-16
> URL: https://issues.apache.org/jira/browse/CHAIN-16
> Project: Commons Chain
> Issue Type: Improvement
> Affects Versions: 1.0
> Environment: Operating System: Windows XP
> Platform: PC
> Reporter: sean schofield
> Priority: Minor
>
> There is an interesting limitation when using ChainListener and ConfigRuleSet
> together. ChainListener allows you to specify any RuleSet you wish which is
> nice and flexible. ConfigRuleSet allows you to override certain defaults
> (such as the class to be used to create new instances of Catalog.)
> The problem is when you use these two together. You can specify
> ConfigRuleSet
> as a context init parameter but you can not go the extra step of using the
> conveinance methods to override its defaults. So there is no way to tell
> ChainListener that you want to use the ConfigRuleSet with a specific Catalog
> class (for instance.) The same limitation also applies to ChainServlet.
> What about a scheme where you define an additional context init parameter
> such
> as RULE_SET_PARAMETER? The scheme would be that you could have
> RULE_SET_PARAMETER[1], RULE_SET_PARAMETER[2], etc. The values could be
> defined as method:value and you could use the reflection API to call the
> appropriate methods on the rule set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
