Joseph Kesselman wrote: > Exactly. What I'm looking for -- and you may already have, though you > didn't use it? -- is a generic Configuration which I can configure via
I implemented an easy way to add custom filters to the XNI pipeline in the NekoHTML parser. Perhaps we could add something similar to Xerces2 so that you could just append custom filter components onto the end of the parsing pipeline. Basically, you create an array of XMLDocumentFilter objects and set a custom property on the configuration. Simple. I also extended the XMLComponent interface to add a way for components within NekoHTML to state what the preferred default value of features and properties should be. This is quite useful and removes a lot of the burden from the configuration to *know* all of the settings of the components in order to set appropriate defaults. It would also be nice to have this as part of the standard XMLComponent interface. You can browse the docs for NekoHTML at the following URL: http://www.apache.org/~andyc/nekohtml/doc/index.html Would such functionality solve your problem? -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
