Hi everyone, The beanwriter isn't really that great in writing nice xml output (eg empty elements) and I think all functionality to write nice xml can be managed in a custom contenthandler (there is already a dependency on an xmlparser, so why not use it). Any objections if I replace the current BeanWriter with a new one using a contenthandler. It will have the same functionality and still is based on AbstractWriter and should work as it does now (enough testcases are using the beanwriter, so that should probably be covered).
Any suggestions or knowledge on the fact why the beanwriter was done in the way it currently is in, will help in making a good decision. (I can make it anyway, adding a default ContentHandler to betwixt which exposes the same functionality as the BeanWriter (indention and stuff) (and therefor adding an empty constructor to the SAXHandler which uses this contentHandler) Let me know :) Mvgr, Martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
