You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Bruno Dumon <br...@outerthought.org> on 2003/10/09 20:59:08 UTC
Re: woody block: Failed to execute
pipeline.: java.util.EmptyStackException
On Thu, 2003-10-09 at 20:30, Tony Collen wrote:
> Bruno Dumon wrote:
> > On Tue, 2003-10-07 at 18:20, Carlos Chávez wrote:
> >
> >> Hi to all,
> >>
> >> i'm working with woody,
> >> i'm using WoodyTemplateTransformer,
> >> when the first time i execute one form this work fine, validation is ok
> >> etc,
> >> but the second time i execute other diferent form and i try to submit
> >> this form this is the message is show me and every form is execute after
> >> shown this message too, this happen in the woody form examples:
>
>
> I've recently gotten this same thing, in fact, with the Woody samples.
>
> Running current CVS and "cocoon servlet" :
>
> 1. Browse to http://localhost:8888/
> 2. Samples -> Blocks w/Samples -> Woody
> 3. Click on "Flowscript" under "Basic Samples"
> 4. Click on "form1 action page" to switch to the CSS tab view
> 5. I either get an EmptyStackException here, or after submitting to add
> a new row.
>
> Hope this helps, somehow :)
Ok, thanks, now I'm also able to reproduce the error, though not
precisely as you mention here. I seem to only get it with the flow
examples. Will look a bit closer at it...
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: woody block: Failed to execute pipeline.: java.util.EmptyStackException
Posted by Carlos Chávez <cc...@agsoftware.dnsalias.com>.
Bruno Dumon Escribio :-)
> Could you guys try if changing the "reuse-parsers" parameter in the
> cocoon.xconf to false helps? It seems to do the trick, but I'm unable to
> reproduce the error reliably so I need some confirmation on that.
Hi bruno,
Thank for you help.
we change the parameter to false and all work fine again.
Antonio Gallardo made the commit to the CVS.
Thank again for your tip.
Carlos Chavez
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: woody block: Failed to execute
pipeline.: java.util.EmptyStackException
Posted by Bruno Dumon <br...@outerthought.org>.
On Thu, 2003-10-09 at 20:59, Bruno Dumon wrote:
> On Thu, 2003-10-09 at 20:30, Tony Collen wrote:
> > Bruno Dumon wrote:
> > > On Tue, 2003-10-07 at 18:20, Carlos Chávez wrote:
> > >
> > >> Hi to all,
> > >>
> > >> i'm working with woody,
> > >> i'm using WoodyTemplateTransformer,
> > >> when the first time i execute one form this work fine, validation is ok
> > >> etc,
> > >> but the second time i execute other diferent form and i try to submit
> > >> this form this is the message is show me and every form is execute after
> > >> shown this message too, this happen in the woody form examples:
> >
> >
> > I've recently gotten this same thing, in fact, with the Woody samples.
> >
> > Running current CVS and "cocoon servlet" :
> >
> > 1. Browse to http://localhost:8888/
> > 2. Samples -> Blocks w/Samples -> Woody
> > 3. Click on "Flowscript" under "Basic Samples"
> > 4. Click on "form1 action page" to switch to the CSS tab view
> > 5. I either get an EmptyStackException here, or after submitting to add
> > a new row.
> >
> > Hope this helps, somehow :)
>
> Ok, thanks, now I'm also able to reproduce the error, though not
> precisely as you mention here. I seem to only get it with the flow
> examples. Will look a bit closer at it...
scrap that, it just pops up randomly, but once a form is infected it
keeps giving the error. Strangely enough the logtransformer shows me
that a comment from the XSL pops up in the pipeline SAX events...
Could you guys try if changing the "reuse-parsers" parameter in the
cocoon.xconf to false helps? It seems to do the trick, but I'm unable to
reproduce the error reliably so I need some confirmation on that.
I remeber Stefano & Sylvain wondering about why it was set to false on
the hackaton and changing it... we may just have found the reason ;-)
(see also bugzilla 22795)
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org