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=36439>. 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=36439 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-28 20:42 ------- (In reply to comment #0) > ConfigurationParser has been improved to make it more flexible to setup your > own > custom Dialog classes but you are still constrained to use the default > dialog.dtd. Looking at this further, I don't think the assertion here is actually correct. The Digester instance actually used will validate against the DTD you specify in the header ... and if you use a unique public identifier, plus a system identifier that tells Digester where to find your DTD, it should "just work". Consider the following at the top of one of your configuration files: <DOCTYPE dialogs PUBLIC "-//My Company//DTD My Shale Dialog Configuration 1.0//EN" "my-dialog.dtd"> As long as you include "my-dialog.dtd" in the same directory where your dialog-config.xml file is, your config file will be parsed against your (presumably extended) DTD instead of the standard one. You won't be able to add any new elements (since the Digester instance is still defining the same rules), but any extra attributes you support on the <dialog>, <state>, etc. elements will be matched to corresponding properties on your implementation classes, and will be set appropriately. That's courtesy of the use of SetPropertyRule in the Digester rule set. Leaving the issue open, however, as use cases for general property setting (without wanting the extra work of customizing the DTD) are emerging on the mailing list. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
