On 13.02.2012 22:11, Christopher Schultz wrote:
All,
There are 15 or so custom rule classes in the Tomcat sources for
handling various commons-digester events.
I've only taken a brief glance at their content, but I'm wondering if we
can't replace these classes with an XML-based configuration that the
Digester itself can handle for us.
Such a change would eliminate those classes form our own code base as
well as allow us to remove the package-renamed code from
commons-digester in SVN (of course, we'd still have to re-package
commons-digester for distribution, but at least we'd have less source to
deal with).
Other than some logging (I can see, for instance, that
ConnectorCreateRule emits warnings when setter methods can't be found on
the target class), is there a compelling reason to have source-based
rules instead of configuration-based rules?
Just an information snippet: Simone Tripodi is working in commons land
on a new major version of the digester. So if we would like to use a
"standard" version of the digester now would be a good time to talk to
him about our custom additions.
I don't know enough about the digester to drive this myself, just
noticed some discussion over in commons.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
