cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <jer...@media.demon.co.uk>
Subject Re: Strange behaviour from 2.1.5
Date Thu, 03 Jun 2004 12:37:37 GMT

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
>>>
>>>
>>>
>

Mime
View raw message