Hi, it turned out that the encoding had nothing to do with the error. As you stated, something seems to be messed up with the DOM. I debugged into the FOP source, it chokes after processing the attributes of the fo:root element, for any reason the element name and its namespace uri always is null then.
Though using SAX would surely be worth the effort, in the current project state the FO tree is needed for post-processing. I'll post any new perceptions i may discover. greets michael -----Urspr�ngliche Nachricht----- Von: J.Pietschmann [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 10. Februar 2004 20:52 An: [EMAIL PROTECTED] Betreff: Re: Problems with Saxon -> FOP? Rauh, Michael wrote: > I'm running XSLT transformations from within Java and put the result DOM into > FOP's AWTRenderer. ... That's all working fine with Xalan (from the JDK) and > jd.xslt. But with Saxon 6.5.3 and Saxon 7.8, FOP throws > NullPointerExceptions. > Here's the ouput when using Saxon-6.5.3: ... > [ERROR] Unsupported element encountered: null (Namespace: null). Source > context: unavailable I use Saxon with FOP all the time. However, I use SAX to pipe the transformation result to the FOP driver (see http://xml.apache.org/fop/embedding.html#ExampleXML2PDF) I guess there is a problem with the DOM or the DOM walker implementation, or perhaps you screwed the DOM while postprocessing. If you dont process the transformation result, I recommend using SAX, it's more ressource friendly anyway (less memory). J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
