RE: Namespaces are dropped in XMP stream. XML invalid
Jörn Willhöft <[email protected]> Thu, 7 Nov 2024 13:34:21 +0100 (CET)
| Newsgroups | gmane.text.xml.fop.user |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_9610_1557826606.1730982861616
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
OK, I am a big step further now. The bug appears in Camel (only) if Saxon i=
s used anywhere in the Camel Route. I use Saxon to create the actual FO and=
additional files. The created FO has the namespaces where they belong, but=
somehow Saxon in the classpath seems to confuse the FOP component internal=
ly. Skipping Saxon is not really an option as I need XSLT 2.0.
=20
It is still unclear to me if the problem is in the Camel FOP component or F=
OP itself.
=20
Cheers
J=C3=B6rn Willh=C3=B6ft
------=_Part_9610_1557826606.1730982861616
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<!doctype html>
<html>
<head>=20
<meta charset=3D"UTF-8">=20
</head>
<body>
<div>
OK, I am a big step further now. The bug appears in Camel (only) if Saxo=
n is used anywhere in the Camel Route. I use Saxon to create the actual FO =
and additional files. The created FO has the namespaces where they belong, =
but somehow Saxon in the classpath seems to confuse the FOP component inter=
nally. Skipping Saxon is not really an option as I need XSLT 2.0.
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"default-style">
It is still unclear to me if the problem is in the Camel FOP component o=
r FOP itself.
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"default-style">
Cheers
</div>=20
<div class=3D"io-ox-signature">=20
<p> J=C3=B6rn Willh=C3=B6ft</p>=20
</div>
</body>
</html>
------=_Part_9610_1557826606.1730982861616--