Re: expected behaviour: global vars in flowscript

2005-08-03 Thread Leszek Gawron
Leszek Gawron wrote: Berin Loritsch wrote: Leszek Gawron wrote: If you are trying to apply MVC here you're failing. You should not be calling pages/displayHome.xsp but some displayHome flowscript function. The flowscript function prepares the bean and does cocoon.sendPage( "pages/displayHo

Re: expected behaviour: global vars in flowscript

2005-08-03 Thread Leszek Gawron
Berin Loritsch wrote: Leszek Gawron wrote: If you are trying to apply MVC here you're failing. You should not be calling pages/displayHome.xsp but some displayHome flowscript function. The flowscript function prepares the bean and does cocoon.sendPage( "pages/displayHome" ) which is matched

Re: expected behaviour: global vars in flowscript

2005-08-03 Thread Berin Loritsch
Leszek Gawron wrote: If you are trying to apply MVC here you're failing. You should not be calling pages/displayHome.xsp but some displayHome flowscript function. The flowscript function prepares the bean and does cocoon.sendPage( "pages/displayHome" ) which is matched to: > >

Re: expected behaviour: global vars in flowscript

2005-08-03 Thread Leszek Gawron
Seon Lee wrote: Hey gang, I'd like your input on some anomalous behaviour I am experiencing in my 2.1.7 flowscript. I have a function defined in javascript that expects a global var to be available at the point in time it is invoked. However, this is not the case -- the function is unable to se