Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <4086F509.1070001@gmx.de>
Date: Thu, 22 Apr 2004 00:26:17 +0200
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Flow->Woody->Event->Woody... possible?
References: <r02010100-1033-2ACC8876935711D8A1F80003934594FA@[203.34.243.197]>
In-Reply-To: 
 <r02010100-1033-2ACC8876935711D8A1F80003934594FA@[203.34.243.197]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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.getSubmitWidget().getId() returned the correct value.
>>
>>Does this help?
> 
> Yes, thank you.  In our flowscript we use a woody2.js Form so we
> can use 'form.form' to get the java form within and so can write
> 
>     if ("remove".equals(form.form.getSubmitWidget().getId())) 
>     
> and all is good.
> 
> Note that so far we have been blissfully unaware of any symptoms
> from the problem Marc alluded to: "I really don't know what the
> event-call on the continuations stack will do if you call showForm
> from inside the event-handling" but we are on alert.

Yes, my comment was completely unrelated to the possible problem Marc 
mentioned. It was only about an undefined form.submitId - while I'm 
really interested why form.submitId is different from 
from.getSubmitWidget().getId(), but I had no look into it until now.

Joerg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org