DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26364>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26364 [PATCH] nested <mapper> for <pathconvert> PLUS composite <mapper> ------- Additional Comments From [EMAIL PROTECTED] 2004-02-03 16:44 ------- So, like Selectors, in order to define a reference, for example, you would nest your custom (named) mappers into a <mapper> element... I thought you might say that. Then the two recommended <mapper> specification means become via explicit typedef'd elements and <mapper classname=""> but this is where dynamic configuration needs to be added, is that where you're going? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
