Alex, Could this have something to do with the fact that this particular processor uses W3C.dom and not dom4j?
We were getting the same error with another processor, and they went away when we switched to using dom4j. (readInputAsDOM4J vs readInputAsDOM) Unfortunately, we our node processor needs to use w3c.dom as the Sun MSV JARV interface does not work with dom4j at this time. Peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alessandro Vernet Sent: Thursday, October 23, 2003 1:48 PM To: OXF Users Subject: Re: different behavior with and without debugs calvin smith wrote: > I am running into an error where I see different behavior depending on > whether there are debugs in my xpl files or not. Hi Calvin, There is 90% chance that this is an incorrect behavior. In most cases, when you see exceptions after removing a debug, it is because a processor is generating faulty SAX events. When you have a debug after the output of that processor, OXF internally creates a dom4j document. The dom4j library is quite forgiving and in most cases will create a valid document even if the SAX events are faulty, and then regenerate correct SAX events. Without the "debug", the events will go directly to the next processor, which might not be as forgiving (for instance Xalan will typically throw NPEs). But we'll need to see your specific case to tell for sure. Can you please send us more info, like the exception, and if possible the pipeline in which this is happening? Alex _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
