[CHAIN-16] Suggested enhancement for ChainListener

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.0
• Component/s: XML Configuration

Environment

Operating System: Windows XP
Platform: PC

• Bugzilla Id: 32911
• Assignee: Unassigned
• Reporter: Sean Schofield
• Created: 02/Jan/05 02:52
• Updated: 04/Jul/13 19:34

Description

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.

Issue Links

• is superceded by: CHAIN-76 Adopt Jackson as underlying parser for Configurations