You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Alexander Smirnoff <as...@vistar.ca> on 2002/02/13 00:25:34 UTC
New release 2.0.1 woes. Continue.
Hi,
I'm stuck big time with integration of new 2.0.1 release with my old 2rc1
server implementation. I had some problems with sitemap, but with the
help of Vadim I've got it more or less working. Thanks. Now problem
arised with xsp files...
It appears that if you put "global" method in your XSP file (before the
first element), which does some <xsp:content> output - it results in
empty document. No errors in logfiles or system output - nothing what
could get me a glue about the reason.
I was comparing old translated java sources with new - it seems no
differens. It looks like it happens on basic cocoon implementation level.
Any help?
Thanks,
Alex.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: New release 2.0.1 woes. Continue.
Posted by Alexander Smirnoff <as...@vistar.ca>.
----- Original Message -----
From: "Vadim Gritsenko" <va...@verizon.net>
To: <co...@xml.apache.org>
Sent: Wednesday, February 13, 2002 2:18 PM
Subject: RE: New release 2.0.1 woes. Continue.
> > From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> >
> > OK. I've got it. Thanks.
>
> Welcome.
>
>
> > I understand the motivation to exlude autocomplete is
> > to speed up the pipeline process. So XSP developer
> > must be responsible of consistent closing of his elements
> > if he or she wants to return somewhere from the middle of
> > XSP logic.
>
> Exactly.
Sounds like good motivation for new <xsp:return> tag.
>
> > General note: it seems 2.0.1 compared with 2rc1 is
> > significally slower for more or less complicated XSP.
>
> Can you pinpoint the reason of slowdown? I'm not sure that there are
> significant changes in the XSP machinery between these two versions.
It is just first impression. I dont want to speculate on this until I
will play enough with cocoon.
> Vadim
>
> >
> > Alex.
> >
> >
> > ----- Original Message -----
> > From: "Vadim Gritsenko" <va...@verizon.net>
> > To: <co...@xml.apache.org>
> > Sent: Wednesday, February 13, 2002 1:04 PM
> > Subject: RE: New release 2.0.1 woes. Continue.
> >
> >
> > > > From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> > > >
> > > > Sorry for misleading about the "global" method, - it works fine.
> > > >
> > > > The problem actually is different:
> > > >
> > > > If I put "return" between open and close tags it results in empty
> > > document.
> > > > Look at example:
> > > >
> > > > <xsp:page language="java" xmlns:xsp="http://apache.org/xsp">
> > > > <Sample>
> > > > <xsp:logic>
> > > > if(true)
> > > > return;
> > > > </xsp:logic>
> > > > </Sample>
> > > > </xsp:page>
> > > >
> > > > Quite important feature I would say.
> > >
> > > Return is prohibited in the main method of the XSP. Use it in own
> > > methods if you want, but with care. And even if you use it in the
> main
> > > XSP method (despite the fact that it is not recommended), XSP engine
> can
> > > cover your mistakes if you set autocomplete-documents to true. Of
> course
> > > this feature isn't for free, performance of you system will degrade.
> > >
> > > PS See ServerPagesGenerator javadoc or source for details.
> > >
> > > Vadim
> > >
> > > >
> > > > Alex.
> > > >
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: New release 2.0.1 woes. Continue.
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>
> OK. I've got it. Thanks.
Welcome.
> I understand the motivation to exlude autocomplete is
> to speed up the pipeline process. So XSP developer
> must be responsible of consistent closing of his elements
> if he or she wants to return somewhere from the middle of
> XSP logic.
Exactly.
> General note: it seems 2.0.1 compared with 2rc1 is
> significally slower for more or less complicated XSP.
Can you pinpoint the reason of slowdown? I'm not sure that there are
significant changes in the XSP machinery between these two versions.
Vadim
>
> Alex.
>
>
> ----- Original Message -----
> From: "Vadim Gritsenko" <va...@verizon.net>
> To: <co...@xml.apache.org>
> Sent: Wednesday, February 13, 2002 1:04 PM
> Subject: RE: New release 2.0.1 woes. Continue.
>
>
> > > From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> > >
> > > Sorry for misleading about the "global" method, - it works fine.
> > >
> > > The problem actually is different:
> > >
> > > If I put "return" between open and close tags it results in empty
> > document.
> > > Look at example:
> > >
> > > <xsp:page language="java" xmlns:xsp="http://apache.org/xsp">
> > > <Sample>
> > > <xsp:logic>
> > > if(true)
> > > return;
> > > </xsp:logic>
> > > </Sample>
> > > </xsp:page>
> > >
> > > Quite important feature I would say.
> >
> > Return is prohibited in the main method of the XSP. Use it in own
> > methods if you want, but with care. And even if you use it in the
main
> > XSP method (despite the fact that it is not recommended), XSP engine
can
> > cover your mistakes if you set autocomplete-documents to true. Of
course
> > this feature isn't for free, performance of you system will degrade.
> >
> > PS See ServerPagesGenerator javadoc or source for details.
> >
> > Vadim
> >
> > >
> > > Alex.
> > >
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: New release 2.0.1 woes. Continue.
Posted by Alexander Smirnoff <as...@vistar.ca>.
OK. I've got it. Thanks.
I understand the motivation to exlude autocomplete is
to speed up the pipeline process. So XSP developer
must be responsible of consistent closing of his elements
if he or she wants to return somewhere from the middle of
XSP logic.
General note: it seems 2.0.1 compared with 2rc1 is
significally slower for more or less complicated XSP.
Alex.
----- Original Message -----
From: "Vadim Gritsenko" <va...@verizon.net>
To: <co...@xml.apache.org>
Sent: Wednesday, February 13, 2002 1:04 PM
Subject: RE: New release 2.0.1 woes. Continue.
> > From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> >
> > Sorry for misleading about the "global" method, - it works fine.
> >
> > The problem actually is different:
> >
> > If I put "return" between open and close tags it results in empty
> document.
> > Look at example:
> >
> > <xsp:page language="java" xmlns:xsp="http://apache.org/xsp">
> > <Sample>
> > <xsp:logic>
> > if(true)
> > return;
> > </xsp:logic>
> > </Sample>
> > </xsp:page>
> >
> > Quite important feature I would say.
>
> Return is prohibited in the main method of the XSP. Use it in own
> methods if you want, but with care. And even if you use it in the main
> XSP method (despite the fact that it is not recommended), XSP engine can
> cover your mistakes if you set autocomplete-documents to true. Of course
> this feature isn't for free, performance of you system will degrade.
>
> PS See ServerPagesGenerator javadoc or source for details.
>
> Vadim
>
> >
> > Alex.
> >
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: New release 2.0.1 woes. Continue.
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>
> Sorry for misleading about the "global" method, - it works fine.
>
> The problem actually is different:
>
> If I put "return" between open and close tags it results in empty
document.
> Look at example:
>
> <xsp:page language="java" xmlns:xsp="http://apache.org/xsp">
> <Sample>
> <xsp:logic>
> if(true)
> return;
> </xsp:logic>
> </Sample>
> </xsp:page>
>
> Quite important feature I would say.
Return is prohibited in the main method of the XSP. Use it in own
methods if you want, but with care. And even if you use it in the main
XSP method (despite the fact that it is not recommended), XSP engine can
cover your mistakes if you set autocomplete-documents to true. Of course
this feature isn't for free, performance of you system will degrade.
PS See ServerPagesGenerator javadoc or source for details.
Vadim
>
> Alex.
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: New release 2.0.1 woes. Continue.
Posted by Alexander Smirnoff <as...@vistar.ca>.
Sorry for misleading about the "global" method, - it works fine.
The problem actually is different:
If I put "return" between open and close tags it results in empty document.
Look at example:
<xsp:page language="java" xmlns:xsp="http://apache.org/xsp">
<Sample>
<xsp:logic>
if(true)
return;
</xsp:logic>
</Sample>
</xsp:page>
Quite important feature I would say.
Alex.
----- Original Message -----
From: "Vadim Gritsenko" <va...@verizon.net>
To: <co...@xml.apache.org>
Sent: Tuesday, February 12, 2002 6:55 PM
Subject: RE: New release 2.0.1 woes. Continue.
> Send in simple test file, couple of lines.
>
> Vadim
>
> > -----Original Message-----
> > From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> > Sent: Tuesday, February 12, 2002 6:26 PM
> > To: cocoon-users@xml.apache.org
> > Subject: New release 2.0.1 woes. Continue.
> >
> > Hi,
> >
> > I'm stuck big time with integration of new 2.0.1 release with my old
> 2rc1
> > server implementation. I had some problems with sitemap, but with the
> > help of Vadim I've got it more or less working. Thanks. Now problem
> > arised with xsp files...
> >
> > It appears that if you put "global" method in your XSP file (before
> the
> > first element), which does some <xsp:content> output - it results in
> > empty document. No errors in logfiles or system output - nothing what
> > could get me a glue about the reason.
> >
> > I was comparing old translated java sources with new - it seems no
> > differens. It looks like it happens on basic cocoon implementation
> level.
> >
> > Any help?
> >
> > Thanks,
> > Alex.
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: New release 2.0.1 woes. Continue.
Posted by Vadim Gritsenko <va...@verizon.net>.
Send in simple test file, couple of lines.
Vadim
> -----Original Message-----
> From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> Sent: Tuesday, February 12, 2002 6:26 PM
> To: cocoon-users@xml.apache.org
> Subject: New release 2.0.1 woes. Continue.
>
> Hi,
>
> I'm stuck big time with integration of new 2.0.1 release with my old
2rc1
> server implementation. I had some problems with sitemap, but with the
> help of Vadim I've got it more or less working. Thanks. Now problem
> arised with xsp files...
>
> It appears that if you put "global" method in your XSP file (before
the
> first element), which does some <xsp:content> output - it results in
> empty document. No errors in logfiles or system output - nothing what
> could get me a glue about the reason.
>
> I was comparing old translated java sources with new - it seems no
> differens. It looks like it happens on basic cocoon implementation
level.
>
> Any help?
>
> Thanks,
> Alex.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>