You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2005/01/01 18:52:47 UTC

DO NOT REPLY [Bug 32911] New: - [chain] Suggested enhancement for ChainListener

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32911>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32911

           Summary: [chain] Suggested enhancement for ChainListener
           Product: Commons
           Version: 1.0 Final
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: chain
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: sean.schofield@gmail.com


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.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org