I agree with Andreas' observations. Looking at the source code of 0.94, the SAX delegate is probably null which would suggest that this Caucho SAXBuilder class didn't call startDocument() before starting with startElement() calls. So, probably a breach of the SAX ContentHandler contract by the caller.
On 16.04.2008 15:47:03 andreas.delmelle wrote: > >----- Oorspronkelijk bericht ----- > >Van: pdiop [mailto:[EMAIL PROTECTED] > > > > Hi, > > Note that Chris has asked a *FO*, not a stylesheet. Reason why we always ask > the *result* of the XSL transform, is that the step of transforming the base > XML into FO is actually not done by FOP. > On top of that, we cannot possibly reproduce your issue with a stylesheet > alone. We'd need at least the included stylesheet and a sample XML. > > >I am using Fop 0.94 with Resin 2.1.17 an Java 1.4. > > Java 1.4.2? Which build? Is it the Sun JVM, or a different vendor? > > > > >I am not exactly using a fo file ut a xslt with fo inside and a xml, here is > >the sample of the xslt file: > <snip /> > > > >I must also say that the program is running fine in a standalone version > >(web project) but once I integrate to a bigger project with lot of things in > >it I get the error. > > I don't think the problem is situated in the FO itself. > > I suspect the issue is caused by the combination of XML parser and XSLT > processor in the environment. Sun Java, for example, ships with versions of > Xerces and Xalan, and in some (mainly older) builds, the included versions > are a bit buggy. > > Try to make sure that the 'bigger' environment is using the same combination > as in your local test. No idea how to configure this in Resin, but for the > standard Java way, google around for 'Java endorsed' or 'Java bootclasspath'. > > > HTH! > > Cheers > > Andreas Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
