Re "mixed content": * Justin, could you please post your proposed implementation either on this list, or attached to the bugzilla entry? Or have a look at my proposal and indicate whether that works for you? * Craig, you were going to have a look at this, I believe? All comments welcome... * Robert, you said in an email: "i have some possible concerns but i'll need to go through the proposed code". Can you spell out these concerns?
I'd be happy with a compromise on this feature. As the change has been committed to keep a stack of matched rules, I *believe* that digester subclasses can now override the startElement method to provide exactly what my patch does. So maybe we can just document this approach somewhere (eg by creating code in the examples subdir). I'll try to implement this approach soon, and post the code if successful.
I think it would be nice in the long-term to provide "mixed content" support without subclassing digester, but for now the subclassing seems a reasonable solution.
Any opinions?
documentation plus an example would be a good way to postpone the issue. it may be easier to decide on this after the release. it's probably not a big a priority (for me) as logging but maybe i'll round to it before the release happens.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
