Re: Strange behaviour from 2.1.5

2004-06-03 Thread Pier Fumagalli
On 3 Jun 2004, at 10:52, Jeremy Quinn wrote: Hi All I just upgraded an existing project to 2.1.5 and am experiencing some strange problems with FlowScript. [...] What was worse was that these messages would GO AWAY on reload ! [...] I suspect the new caching system (which throws exceptions on

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Jeremy Quinn
On 3 Jun 2004, at 13:48, Antonio Gallardo wrote: Hi Jeremy: Thanks for the answer. Can be the problem related to switching between sitemaps? ie: Lets said your are in a form in the record.xmap and from inside a flow you call a function from search.xmap. no, this kind of thing is not being done apar

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Antonio Gallardo
Hi Jeremy: Thanks for the answer. Can be the problem related to switching between sitemaps? ie: Lets said your are in a form in the record.xmap and from inside a flow you call a function from search.xmap. Reading again your problem, is posible you have similar function names between the .js files

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Andreas Schmid
I just read it to late that you're using FlowScript... not JavaFlow... In JavaFlow you declare classes, so you are abel to create Variables from outside the functions which we call global, because you can use them all over the class... Jeremy Quinn wrote: On 3 Jun 2004, at 13:02, Andreas Schmid

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Jeremy Quinn
On 3 Jun 2004, at 13:02, Andreas Schmid wrote: I know that this will not fix the "bug". But we've postet this bug 2 Days ago and till now there is no answer. So we needed to make a workaround to continue working. What i did was just telling you who to do a workaround... :-) Sorry for my misunder

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Jeremy Quinn
On 3 Jun 2004, at 13:10, Antonio Gallardo wrote: Hi Jeremy: I have another problem, but maybe it is related. I have a question. Are you using subsitemaps? Can you explain how are distributed the .js files? Yes we are using sub-sitemaps. "sitemap.xmap" : cocoon's main sitemap mounts our top

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Antonio Gallardo
Hi Jeremy: I have another problem, but maybe it is related. I have a question. Are you using subsitemaps? Can you explain how are distributed the .js files? Best Regards, Antonio Gallardo Jeremy Quinn dijo: > Hi All > > I just upgraded an existing project to 2.1.5 and am experiencing some > str

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Andreas Schmid
I know that this will not fix the "bug". But we've postet this bug 2 Days ago and till now there is no answer. So we needed to make a workaround to continue working. What i did was just telling you who to do a workaround... :-) CYA Andreas Jeremy Quinn wrote: On 3 Jun 2004, at 11:53, Andreas Sc

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Jeremy Quinn
On 3 Jun 2004, at 11:53, Andreas Schmid wrote: Just try to declare your variables as globals outside the functions. This should help that the JavaFlow willl Work... Many thanks for your reply, but I cannot see how this will solve the problem. These are flowscripts that are known to work (in 2.1.4

Re: Strange behaviour from 2.1.5

2004-06-03 Thread Andreas Schmid
Just try to declare your variables as globals outside the functions. This should help that the JavaFlow willl Work... Jeremy Quinn wrote: Hi All I just upgraded an existing project to 2.1.5 and am experiencing some strange problems with FlowScript. I am seeing a lot of these errors: org.apache.av

Strange behaviour from 2.1.5

2004-06-03 Thread Jeremy Quinn
Hi All I just upgraded an existing project to 2.1.5 and am experiencing some strange problems with FlowScript. I am seeing a lot of these errors: org.apache.avalon.framework.CascadingRuntimeException: "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line 203: uncaught JavaScript ex