Never create continuations in an event handler. If you do the
continuation stack is only that of the event handler and the original
script will _not_ resume when the event handler completes. In other
words the call stack looks like this
Java (FlowInterpreter.callFunction("myFunction")) => JS (m
On 21.04.2004 07:45, Steve Steinitz wrote:
I had the same problem yesterday too:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108238973125352&w=4
and fixed it by changing the order of the form widgets in the definition.
Furthermore my form.submitId was also null at the end, while
form.getSubm
Hello Joerg
On Tuesday, 20 April 2004 at 9:52am, Joerg Heinicke wrote:
>On 20.04.2004 09:44, Steve Steinitz wrote:
>> We couldn't find that example but here is what we've done:
>>
>>
>>Remove
>>
>>
>> and in our xsp
>>
>>
>>
>> and in the flow
>>
>> if ("remove
Joerg Heinicke wrote:
On 20.04.2004 09:44, Steve Steinitz wrote:
We couldn't find that example but here is what we've done:
Remove
and in our xsp
and in the flow
if ("remove".equals(form.submitId)) {
...
}
This condition was never true so I logge
Steve Steinitz wrote:
Hello List,
Thank you for your reply to my colleague's query, Marc.
Marc Portier wrote:
not trying to subvert the relation between the form and it's
actions you should 'complete' the form and go onto the next one
change the action into:
Remove
and then after
On 20.04.2004 09:44, Steve Steinitz wrote:
We couldn't find that example but here is what we've done:
Remove
and in our xsp
and in the flow
if ("remove".equals(form.submitId))
{
...
}
This condition was never true so I logged the value of
form.su
Hello List,
Thank you for your reply to my colleague's query, Marc.
Marc Portier wrote:
>not trying to subvert the relation between the form and it's
>actions you should 'complete' the form and go onto the next one
>
>change the action into:
>
> Remove
>
>
>and then after the for
Phil Blake wrote:
Hiya,
In flow I create a woody form containing a list and a remove button. It
is shown using the form.showForm(...) method.
When the remove button is pressed a woody javascript event is triggered.
The script runs and builds a new form and again shows it using
form.showForm
Hiya,
In flow I create a woody form containing a list and a remove button. It is shown using the form.showForm(...) method.
When the remove button is pressed a woody javascript event is triggered.
The script runs and builds a new form and again shows it using form.showForm()
However, the previo
