BTW you could use cocoon.processPipelineTo() to create your script and then use eval() to load it.
Regards,
Chris
[EMAIL PROTECTED] wrote:
Sylvain,
Thanks for the tip. It turns out that I must touch *both* the script file containing the load(...) instruction and the sitemap (!) before my .js file is properly updated. I did not try touching the "main" script file; this would be woody.js, which is in a jar.
It's a hack, but it works, and now I can try a few more things...
--Michael
Sylvain Wallez <[EMAIL PROTECTED]> wrote on 09/03/2003 12:47:59 AM:
> [EMAIL PROTECTED] wrote:
>
> >
> > Hi,
> >
> > I'm playing with Woody and Flowscript and want to include some dynamic
> > javascript as Flowscript. The javascript would be generated by
> > transforming some XML markup into script. So I tried:
> > cocoon.load("cocoon:/getControllerLogic");
> > from somewhere in Woody's flowscript.
> >
> > But it seems that Flowscripts are loaded once and only once when the
> > sitemap is loaded. Is this correct? Or am I doing something wrong?
>
>
> I've seen this behaviour with static files : FlowScript doesn't seem to
> check changes on scripts loaded with cocoon.load().
>
> This is a bug, and the current workaround is to touch the main script file.
>
> > Or maybe tryin to use dynamic flowscript is just bad magic? I'm
> > playing around with the thought of supporting hundreds or thousands of
> > forms, each with (potentially) their own unique controller logic....
>
>
> Looks yummy ;-)
>
> Sylvain
>
> --
> Sylvain Wallez Anyware Technologies
> http://www.apache.org/~sylvain http://www.anyware-tech.com
> { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
> Orixo, the opensource XML business alliance - http://www.orixo.com
>
>
