RTFProcessor produces invalid XSL-FO in WebLogic

Question

I've been writing an application that uses the RTProcessor class to process an rtf file into XML, which I can then parse to information about the report layout.
While developing on tomcat this worked fine. However for production we will be deploying on WebLogic. WebLogic seems to be using a different XML parser that is stricter than tomcats so when using the application the XML parser throws an error when parsing the XSL-FO.
The problem is that XSL-FO is not valid XML as it contains an invalid character on the line:
<xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, concat($_XDODFOVERRIDE,'',$_XDOCURMASKS,'',$_XDONFSEPARATORS))"/>
So my first question is: Is there a way to stop this element from being generated in the XSL-FO? This seems to have been looked at in this thread but without much of a conclusion:
BI Publisher produces invalid XSL:FO stylesheet
My second question: I don't understand how Tomcat can parse the XML and WebLogic can't. I'm deploying the same code so I'd assumed it would be using the same parser. As a work around around is it possible to configure WebLogic to use the same parser as tomcat? The relevant code I'm using is posted below:
ByteArrayOutputStream templateOutputStream = new ByteArrayOutputStream();
               RTFProcessor rtfProcessor = new RTFProcessor(
                         new FileInputStream(template.getTemplateFile())
               rtfProcessor.setOutput(templateOutputStream);
               rtfProcessor.process();
               logger.debug(this.className + " - " + methodName +
                         ":#2 XSL-FO : " + templateOutputStream.toString());
               DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
               DocumentBuilder db = dbf.newDocumentBuilder();
               // parse using builder to get DOM representation of the XML file
               Document dom = db.parse(new ByteArrayInputStream(templateOutputStream.toByteArray()));
Thanks in advance.

Answer 1

Hi,
Thanks for your reply, After debugging the application carefully in Tomcat and Weblogic it became apparent that weblogic was using it's preferred XML parsers when parsing my XML.
In Tomcat has a different order or precedence for its class loader so it was parsing my XML with the oracle.xml package, Weblogic was instead using its own weblogic.xml parser. So I had to set up a weblogic-application.xml file to control this.
If you're right that the XML is valid, then this looks like there is a bug in the weblogic parser. I'm not at work at the moment but if you want more details I can get you them next week.
Thanks.