I think there are two distinct problems here:
1. Possibly, a caching bug related to passing parameters between pages.
2. Most likely, some incorrect XSLT that tries to generate, well, text outside of a root element. Going through the debug processor may hide this error.
For problem #1, we need something that we can reproduce. Are you using 2.2 or a post-2.2 build?
For problem #2, I would double-check the XSLT code to make sure it does not indeed output invalid XML. It appears that XSLT transformers are pretty dumb when it comes to making sure that they are generating correct SAX events.
-Erik
Peter Charles wrote:
> Hi guys, > > I am having a little problem when removing debug statements. Basically > with out debug statements certain parts of our app break. > > I seem to remember this same problem happening before, but I do not > remember the resolutions. > > The first instance of this happening is on the input parameter to a page > B's model xpl. The input is declared and the xudated xform from the > referring page (A) is then used within the model. The page A's > controller entry has two results, each result corresponds to updating a > different field of page B's xform. > > If the first of page A's results is executed, page B's model will > notreceive the xupdated xform with out a debug being in place. > > If the second result is executed, page B's model receives the updated > xform with out a problem. > > The second instance of a debug problem occurs when using the xslt > processor. If there is not a debug on the output, then a: > > org.xml.sax.SAXException: Warning: can't output text before document > element! Ignoring...page > > Error is thrown. I believe this is the error we have had before. > > Thanks > > Peter
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
