Could this have something to do with the fact that this particular
processor uses W3C.dom and not dom4j?
Hi Peter,
dom4j is very forgiving. So when writing your custom processors, reading the input with the dom4j API will shield you against incorrect SAX, to a certain level. And by that I mean that your processor might continue to work, even if it is fed with invalid SAX. But ultimately, this is not what you want. You want to fix the code that is generating invalid SAX. So there is definitely nothing wrong about using the DOM API, if you need to, or if this is the most convenience in your case.
Alex
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
