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

[bu...@apache.org]

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





------- Additional Comments From Joe@Germuska.com  2005-01-04 23:25 -------
It seems kind of awkward.  My inclination would be to specify this in XML
somehow.  It would be easy enough to add a "className" attribute to catalog and
chain which would be used as the type to instantiate; this is more burden if you
want to repeatedly use the same alternate class, but is otherwise effective and
available to the ChainListener but also other uses.  

We could also consider a "defaults" element which could wrap a block of config
XML.  A simple ObjectCreate/SetProperties rule could put a "Defaults" bean in
the digester stack, and other rules which could peek back through the digester
stack looking for the instance.  If we did this, we would either have to require
that it only wrap catalogs, or change the ConfigRegisterRule to look harder for
a chain or catalog, instead of always assuming that it was the "top minus 1"
object in the Digester stack.


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