xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas L. Delmelle" <a_l.delme...@pandora.be>
Subject RE: Problems with Saxon -> FOP?
Date Mon, 09 Feb 2004 19:53:31 GMT
> -----Original Message-----
> From: Rauh, Michael [mailto:Michael.Rauh@NDSatcom.com]
>
>
> are there known problems with the interoperability of specific
> XSLT processors and FOP?
>

Phew! What a question... I've certainly thought lots of times about using
Saxon with FOP instead of Xalan, but haven't really tried. If you feel like
documenting your findings and posting them here, any input gladly
appreciated!

> I'm running XSLT transformations from within Java and put the
> result DOM into FOP's AWTRenderer. My source documents are mainly
> DocBook instances, but also other ones.
>

Hmm, and do all these documents render properly when you run them
standalone?

> 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:
>
>
> [INFO] setting up fonts
> [ERROR] Unsupported element encountered: null (Namespace: null).
> Source context: unavailable
<snip />
> When I serialize the FO Document the XSLT processors built,
> they're looking exactly the same for all processors though.
>
> Considering FOP, I tried both 0.20.5 and the 0.20.2-maintain branch.
>
> Any hints appreciated.

Could you try the following:

- run the XSLT (try both processors)
- run the resulting FOs through FOP via the command-line with -d for
debugging, and see what comes out (if this gives no problems, someone's
going to have to check out the specifics of Saxon's DOM Output --particular
diffs with Xalan that could explain this? )


Cheers,

Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org


Mime
View raw message