You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by C Bram Dit Saint Amand <sc...@comp.leeds.ac.uk> on 2003/07/29 15:42:29 UTC
problem
Hello Mailing list,
I came across a problem with cocoon 2.1m3 & cocoon CVS, but the thing
works with latest cocoon 2.0:
In cocoon 2.1, when I do a <xsl:variable name="foo"
select="document('foo.xml')/bar"/> inside a stylesheet, when the
stylesheet is processed, the entire content of foo.xml is directly
displayed on the screen (not even the sub-content between <bar> and
</bar>). Furthermore, the rest of the stylesheet templates seem to be
ignored.
But in cocoon 2.0, the content of 'foo.xml' between <bar> and </bar> is
only displayed when I say so (e.g. by a <xsl:value-of select="$foo"/>). So
in cocoon 2.0 it works as I want it to.
Is this a bug, or is it a normal behaviour of cocoon 2.1?
What is even more surprising is that the latest Forrest CVS uses this type
of variables with the latest cocoon 2.1 CVS, and it aparently works!!!
That's why the problem probably comes form me messing up somewhere...
If someone could look at this it would be greatly appreciated.
/Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: problem
Posted by Joerg Heinicke <jo...@gmx.de>.
C Bram Dit Saint Amand wrote:
> You are right Joerg, I was experiencing the bug in XSLTC you mentionned,
> since it works with Xalan.
> So I thank you very much for your help, really.
Ok.
> But this kind of problem shows once more how Cocoon cannot be considered
> as a serious framework for industry projects. I'm sorry but that's true
> when there are such enormous bugs in the latest *supposedly stable*
> 2.1 distribution...
No! Cocoon 2.1 was never marked as stable. Today there was an
announcement about RC 1. The latest stable release is 2.0.4 - with Xalan
as default. Yes, the Cocoon 2.1 core is more or less stable. But we
depend also on external libraries like Xalan and XSLTC. And we don't
offer a commercial product, where one organization is "responsible" -
that's open source, you have to live with the one or the other limitation.
> Why was XSLTC made the default transformer if such a bug is known? I don't
> get it...
Because XSLTC is supposed to be the better while faster transformer.
Furthermore we help the Xalan community to test their product. The bug
is already found and will be fixed anytime hopefully. You can higher the
"pressure" on fixing this bug e.g. by voting on this bug (again the URL:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381).
> I'm looking forward to when Cocoon will be usable without having to find
> workarounds to avoid its inherent bugs. Maybe when my project will be
> over...
I'm sorry if this is your thinking. But you can't use much open source
software then.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: problem
Posted by C Bram Dit Saint Amand <sc...@comp.leeds.ac.uk>.
You are right Joerg, I was experiencing the bug in XSLTC you mentionned,
since it works with Xalan.
So I thank you very much for your help, really.
But this kind of problem shows once more how Cocoon cannot be considered
as a serious framework for industry projects. I'm sorry but that's true
when there are such enormous bugs in the latest *supposedly stable*
2.1 distribution...
Why was XSLTC made the default transformer if such a bug is known? I don't
get it...
I'm looking forward to when Cocoon will be usable without having to find
workarounds to avoid its inherent bugs. Maybe when my project will be
over...
On Wed, 30 Jul 2003, Joerg Heinicke wrote:
> Seems to be a problem with XSLTC:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381. Unlike Cocoon
> 2.0 XSLTC is the default processor in Cocoon 2.1. Try to force the
> transformer type to xalan if you must use top-level xsl:variable.
>
> Joerg
>
> C Bram Dit Saint Amand wrote:
>
> > Hello Mailing list,
> >
> >
> > I came across a problem with cocoon 2.1m3 & cocoon CVS, but the thing
> > works with latest cocoon 2.0:
> >
> > In cocoon 2.1, when I do a <xsl:variable name="foo"
> > select="document('foo.xml')/bar"/> inside a stylesheet, when the
> > stylesheet is processed, the entire content of foo.xml is directly
> > displayed on the screen (not even the sub-content between <bar> and
> > </bar>). Furthermore, the rest of the stylesheet templates seem to be
> > ignored.
> >
> > But in cocoon 2.0, the content of 'foo.xml' between <bar> and </bar> is
> > only displayed when I say so (e.g. by a <xsl:value-of select="$foo"/>). So
> > in cocoon 2.0 it works as I want it to.
> >
> > Is this a bug, or is it a normal behaviour of cocoon 2.1?
> > What is even more surprising is that the latest Forrest CVS uses this type
> > of variables with the latest cocoon 2.1 CVS, and it aparently works!!!
> > That's why the problem probably comes form me messing up somewhere...
> >
> >
> > If someone could look at this it would be greatly appreciated.
> >
> >
> > /Chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: problem
Posted by Joerg Heinicke <jo...@gmx.de>.
Seems to be a problem with XSLTC:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381. Unlike Cocoon
2.0 XSLTC is the default processor in Cocoon 2.1. Try to force the
transformer type to xalan if you must use top-level xsl:variable.
Joerg
C Bram Dit Saint Amand wrote:
> Hello Mailing list,
>
>
> I came across a problem with cocoon 2.1m3 & cocoon CVS, but the thing
> works with latest cocoon 2.0:
>
> In cocoon 2.1, when I do a <xsl:variable name="foo"
> select="document('foo.xml')/bar"/> inside a stylesheet, when the
> stylesheet is processed, the entire content of foo.xml is directly
> displayed on the screen (not even the sub-content between <bar> and
> </bar>). Furthermore, the rest of the stylesheet templates seem to be
> ignored.
>
> But in cocoon 2.0, the content of 'foo.xml' between <bar> and </bar> is
> only displayed when I say so (e.g. by a <xsl:value-of select="$foo"/>). So
> in cocoon 2.0 it works as I want it to.
>
> Is this a bug, or is it a normal behaviour of cocoon 2.1?
> What is even more surprising is that the latest Forrest CVS uses this type
> of variables with the latest cocoon 2.1 CVS, and it aparently works!!!
> That's why the problem probably comes form me messing up somewhere...
>
>
> If someone could look at this it would be greatly appreciated.
>
>
> /Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org