You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jens Maukisch <co...@maukisch.net> on 2006/08/08 22:08:42 UTC
Problems with XInclude and Xalan
Hi,
we've had some problems lately which seem to occur
in a combination of XInclude and some XSLT transformations
with Xalan (XSLTC and the normal mode).
One Problem for Example is that we have 'empty' element
< xmlns="foo" attr="xyz">foo bar</> after a quiet normal
copy-all (xsl:template match="node()|@*) transformation
(everything is copied ok, exept some tags) or NPEs which
cause is unclear.
In every case we fist have an XInclude transformation and
then a normal XSLT-Transformation. The included XML seems
to be okay, but we have many different namespaces.
ATM I've no simple example to reproduce the behaviour,
but has anyone seen something like this before and a
hint what the problem is?
We have a Cocoon 2.1.9 and Java 5 on Linux and Windows.
Thanks for your help in advance
--
* best regards
* Jens Maukisch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problems with XInclude and Xalan
Posted by Reinhard Poetz <re...@apache.org>.
Jens Maukisch wrote:
> Hi,
>
> we've had some problems lately which seem to occur
> in a combination of XInclude and some XSLT transformations
> with Xalan (XSLTC and the normal mode).
> One Problem for Example is that we have 'empty' element
> < xmlns="foo" attr="xyz">foo bar</> after a quiet normal
> copy-all (xsl:template match="node()|@*) transformation
> (everything is copied ok, exept some tags) or NPEs which
> cause is unclear.
> In every case we fist have an XInclude transformation and
> then a normal XSLT-Transformation. The included XML seems
> to be okay, but we have many different namespaces.
>
> ATM I've no simple example to reproduce the behaviour,
> but has anyone seen something like this before and a
> hint what the problem is?
Unfortunatly not. Have you tried to use the LogTransformer to get a detailed
report about what's actually in the SAX stream?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org