You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jeremy Quinn <je...@media.demon.co.uk> on 2004/06/03 11:52:00 UTC
Strange behaviour from 2.1.5
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 exception: at handleForm
(resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line 203):
"uploadImage" is not a function.
These appear to be erroneous (it clearly IS a function and worked fine
under previous versions), and nearly random in appearance (sometimes
you get this sometimes you don't).
The next problem I started seeing was errors related to instantiating
Java Objects from Flow, where the flow engine would complain that the
package paths were ambiguous. What was worse was that these messages
would GO AWAY on reload !!!!!
I suspect the new caching system (which throws exceptions on shutdown).
I am using the Release version of Cocoon 2.1.5 (we always attempt to
only use release versions for development and we have several people
working on the same project at the same time, and that makes it far
easier).
Are there any known issues with 2.1.5 release that may be causing this
behaviour ?
Many thanks for any suggestions.
regards Jeremy
Re: Strange behaviour from 2.1.5
Posted by Andreas Schmid <co...@sa-lsa.com>.
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 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 misunderstanding.
>
> You are saying that adding any old global variable to each of the
> flowscript magically solves the problem?
>
> Remind me, is there a special syntax for global variables ?
>
> thanks
>
> regards Jeremy
>
>
>> Jeremy Quinn wrote:
>>
>>>
>>> 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 and
>>> eventually in 2.1.5).
>>>
>>> The functionality of the scripts does not require nor want global
>>> variables.
>>>
>>> regards Jeremy
>>>
>>>> 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.avalon.framework.CascadingRuntimeException:
>>>>> "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line
>>>>> 203: uncaught JavaScript exception: at handleForm
>>>>> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line
>>>>> 203): "uploadImage" is not a function.
>>>>>
>>>>> These appear to be erroneous (it clearly IS a function and worked
>>>>> fine under previous versions), and nearly random in appearance
>>>>> (sometimes you get this sometimes you don't).
>>>>>
>>>>> The next problem I started seeing was errors related to
>>>>> instantiating Java Objects from Flow, where the flow engine would
>>>>> complain that the package paths were ambiguous. What was worse was
>>>>> that these messages would GO AWAY on reload !!!!!
>>>>>
>>>>> I suspect the new caching system (which throws exceptions on
>>>>> shutdown).
>>>>>
>>>>> I am using the Release version of Cocoon 2.1.5 (we always attempt
>>>>> to only use release versions for development and we have several
>>>>> people working on the same project at the same time, and that
>>>>> makes it far easier).
>>>>>
>>>>> Are there any known issues with 2.1.5 release that may be causing
>>>>> this behaviour ?
>>>>>
>>>>>
>>>>> Many thanks for any suggestions.
>>>>>
>>>>> regards Jeremy
>>>>
>>>>
>>>>
>>>>
>>
Re: Strange behaviour from 2.1.5
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
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 misunderstanding.
You are saying that adding any old global variable to each of the
flowscript magically solves the problem?
Remind me, is there a special syntax for global variables ?
thanks
regards Jeremy
> Jeremy Quinn wrote:
>
>>
>> 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 and eventually
>> in 2.1.5).
>>
>> The functionality of the scripts does not require nor want global
>> variables.
>>
>> regards Jeremy
>>
>>> 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.avalon.framework.CascadingRuntimeException:
>>>> "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line
>>>> 203: uncaught JavaScript exception: at handleForm
>>>> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line
>>>> 203): "uploadImage" is not a function.
>>>>
>>>> These appear to be erroneous (it clearly IS a function and worked
>>>> fine under previous versions), and nearly random in appearance
>>>> (sometimes you get this sometimes you don't).
>>>>
>>>> The next problem I started seeing was errors related to
>>>> instantiating Java Objects from Flow, where the flow engine would
>>>> complain that the package paths were ambiguous. What was worse was
>>>> that these messages would GO AWAY on reload !!!!!
>>>>
>>>> I suspect the new caching system (which throws exceptions on
>>>> shutdown).
>>>>
>>>> I am using the Release version of Cocoon 2.1.5 (we always attempt
>>>> to only use release versions for development and we have several
>>>> people working on the same project at the same time, and that makes
>>>> it far easier).
>>>>
>>>> Are there any known issues with 2.1.5 release that may be causing
>>>> this behaviour ?
>>>>
>>>>
>>>> Many thanks for any suggestions.
>>>>
>>>> regards Jeremy
>>>
>>>
>>>
>
Re: Strange behaviour from 2.1.5
Posted by Andreas Schmid <co...@sa-lsa.com>.
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 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 and eventually
> in 2.1.5).
>
> The functionality of the scripts does not require nor want global
> variables.
>
> regards Jeremy
>
>> 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.avalon.framework.CascadingRuntimeException:
>>> "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line
>>> 203: uncaught JavaScript exception: at handleForm
>>> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line
>>> 203): "uploadImage" is not a function.
>>>
>>> These appear to be erroneous (it clearly IS a function and worked
>>> fine under previous versions), and nearly random in appearance
>>> (sometimes you get this sometimes you don't).
>>>
>>> The next problem I started seeing was errors related to
>>> instantiating Java Objects from Flow, where the flow engine would
>>> complain that the package paths were ambiguous. What was worse was
>>> that these messages would GO AWAY on reload !!!!!
>>>
>>> I suspect the new caching system (which throws exceptions on shutdown).
>>>
>>> I am using the Release version of Cocoon 2.1.5 (we always attempt to
>>> only use release versions for development and we have several people
>>> working on the same project at the same time, and that makes it far
>>> easier).
>>>
>>> Are there any known issues with 2.1.5 release that may be causing
>>> this behaviour ?
>>>
>>>
>>> Many thanks for any suggestions.
>>>
>>> regards Jeremy
>>
>>
>>
Re: Strange behaviour from 2.1.5
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
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 and eventually
in 2.1.5).
The functionality of the scripts does not require nor want global
variables.
regards Jeremy
> 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.avalon.framework.CascadingRuntimeException:
>> "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line
>> 203: uncaught JavaScript exception: at handleForm
>> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line
>> 203): "uploadImage" is not a function.
>>
>> These appear to be erroneous (it clearly IS a function and worked
>> fine under previous versions), and nearly random in appearance
>> (sometimes you get this sometimes you don't).
>>
>> The next problem I started seeing was errors related to instantiating
>> Java Objects from Flow, where the flow engine would complain that the
>> package paths were ambiguous. What was worse was that these messages
>> would GO AWAY on reload !!!!!
>>
>> I suspect the new caching system (which throws exceptions on
>> shutdown).
>>
>> I am using the Release version of Cocoon 2.1.5 (we always attempt to
>> only use release versions for development and we have several people
>> working on the same project at the same time, and that makes it far
>> easier).
>>
>> Are there any known issues with 2.1.5 release that may be causing
>> this behaviour ?
>>
>>
>> Many thanks for any suggestions.
>>
>> regards Jeremy
>
>
Re: Strange behaviour from 2.1.5
Posted by Andreas Schmid <co...@sa-lsa.com>.
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.avalon.framework.CascadingRuntimeException:
> "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line
> 203: uncaught JavaScript exception: at handleForm
> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line
> 203): "uploadImage" is not a function.
>
> These appear to be erroneous (it clearly IS a function and worked fine
> under previous versions), and nearly random in appearance (sometimes
> you get this sometimes you don't).
>
> The next problem I started seeing was errors related to instantiating
> Java Objects from Flow, where the flow engine would complain that the
> package paths were ambiguous. What was worse was that these messages
> would GO AWAY on reload !!!!!
>
> I suspect the new caching system (which throws exceptions on shutdown).
>
> I am using the Release version of Cocoon 2.1.5 (we always attempt to
> only use release versions for development and we have several people
> working on the same project at the same time, and that makes it far
> easier).
>
> Are there any known issues with 2.1.5 release that may be causing this
> behaviour ?
>
>
> Many thanks for any suggestions.
>
> regards Jeremy
Re: Strange behaviour from 2.1.5
Posted by Pier Fumagalli <pi...@betaversion.org>.
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 shutdown)
If you remember, all our problems with the VNUNET project got sorted
out when we started using non-caching pipelines, weirdly enough...
All those components that didn't actually render correctly after a
little while, and that (magically) re-appeared on reloads...
Maybe there is something wrong with the cache????????
Pier (just throwing ideas on the wall out here)
Re: Strange behaviour from 2.1.5
Posted by Jeremy Quinn <je...@luminas.co.uk>.
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
apart from authentication (which is not fully applied yet anyway) we do
not re-use across sub-sitemaps via flow-called pipelines.
> Reading again your problem, is posible you have similar function names
> between the .js files? Maybe this is the problem.
No, I avoid this like the plague ;)
We have all unique function names across all of the flowscript files
> I have a similar problem, but now I think it is quite diferent. My
> problem
> is not related to 2.1.5, it is related to lastest CVS.
OK, we are trying to avoid using non-release versions as it makes sure
all developers are using exactly the same environment.
regards Jeremy
Re: Strange behaviour from 2.1.5
Posted by Antonio Gallardo <ag...@agssa.net>.
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? Maybe this is the problem.
I have a similar problem, but now I think it is quite diferent. My problem
is not related to 2.1.5, it is related to lastest CVS.
Best Regards,
Antonio Gallardo
Re: Strange behaviour from 2.1.5
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
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-level 'project' sitemap :
"sitemap.xmap" :
uses 'authentication.js' flowscript
provides views of static XML documents
mounts each sub-section sitemap :
"authenticate.xmap" :
provides authentication services
uses 'authentication.js' flowscript
"record.xmap" :
provides database record viewing services
uses 'records.js' and 'pager.js' flowscript
"search.xmap" :
provides lucene index searching services
uses 'search.js' and 'pager.js' flowscript
"lucene.xmap" :
provides database record indexing services
uses 'lucene.js' flowscript
"upload.xmap" :
provides database record creation and asset uploading services
uses 'upload.js' flowscript
HTH
regards Jeremy
>
> Best Regards,
>
> Antonio Gallardo
>
> Jeremy Quinn dijo:
>> 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 exception: at handleForm
>> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line
>> 203):
>> "uploadImage" is not a function.
>>
>> These appear to be erroneous (it clearly IS a function and worked fine
>> under previous versions), and nearly random in appearance (sometimes
>> you get this sometimes you don't).
>>
>> The next problem I started seeing was errors related to instantiating
>> Java Objects from Flow, where the flow engine would complain that the
>> package paths were ambiguous. What was worse was that these messages
>> would GO AWAY on reload !!!!!
>>
>> I suspect the new caching system (which throws exceptions on
>> shutdown).
>>
>> I am using the Release version of Cocoon 2.1.5 (we always attempt to
>> only use release versions for development and we have several people
>> working on the same project at the same time, and that makes it far
>> easier).
>>
>> Are there any known issues with 2.1.5 release that may be causing this
>> behaviour ?
>>
>>
>> Many thanks for any suggestions.
>>
>> regards Jeremy
>
Re: Strange behaviour from 2.1.5
Posted by Antonio Gallardo <ag...@agssa.net>.
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
> 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 exception: at handleForm
> (resource://org/apache/cocoon/forms/flow/javascript/Form.js, Line 203):
> "uploadImage" is not a function.
>
> These appear to be erroneous (it clearly IS a function and worked fine
> under previous versions), and nearly random in appearance (sometimes
> you get this sometimes you don't).
>
> The next problem I started seeing was errors related to instantiating
> Java Objects from Flow, where the flow engine would complain that the
> package paths were ambiguous. What was worse was that these messages
> would GO AWAY on reload !!!!!
>
> I suspect the new caching system (which throws exceptions on shutdown).
>
> I am using the Release version of Cocoon 2.1.5 (we always attempt to
> only use release versions for development and we have several people
> working on the same project at the same time, and that makes it far
> easier).
>
> Are there any known issues with 2.1.5 release that may be causing this
> behaviour ?
>
>
> Many thanks for any suggestions.
>
> regards Jeremy