I've embedded FOP 0.93 in an Oracle AS 10g (9.0.4) Reports pluggable
destination, which itself is implemented as a J2EE application. Therefore,
FOP is called as part of the already-running J2EE environment.

The problem that I'm having is that the Oracle XML parser blows chunks and
won't properly parse documents in order for FOP to work correctly. I have
everything working properly as long as I put Xerces and Xml-apis in the
pre-boot class path (e.g. "-Xbootclasspath^/p:...") and specifying Xalan as
the TransformFactory (e.g. "...
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transfor
merFactoryImpl).

However, although this configuration works perfectly, Oracle has
specifically declared that it will not be supported. Basically if
Xerces/Xalan ever blows up Oracle Reports, our enterprise's million dollar
support contract is worthless.

Soooooooooooo...  Question: Is there any other way to force FOP to use the
Xalan transformer factory without overriding it for the entire Oracle
Reports application? I may even be allowed the time and resources to create
a FOP patch in order to make this modification if required.

As always, thank you in advance for your thoughts.

Jeff



Reply via email to