Hey Wouter,
 
I was wondering if Chad's pbm regarding select fields wasn't the same as I (except that I sometimes get the setters generated for the lists).
Because I do have a page with two forms and one field displayed as select in a form and hidden in the other form.
It is common to have a select which triggers a refresh (either through _javascript_ or form submit) to synchronize form fields.
Thus I believe it would be nice to fix this as regards issue BPM-124.
 
Regards,
Fred.
----- Original Message -----
Sent: Wednesday, December 15, 2004 7:28 PM
Subject: [Andromda-devel] RE: Bpm4struts + select type for fields

Hi Chad,

 

In order to properly make use of �select� you should always preload the list data in the controller, the way to do this is to defer to a controller operation right before you enter the page containing the �select�, the operation MUST have a parameter with the exact same name and type as the one you have flagged as �select�.

 

Doing this will generate accessors to the select value and corresponding backing list in the operation form interface as well as the actual action form

 

-- Wouter

 


From: Chad Brandon [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 15, 2004 4:10 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Bpm4struts + select type for fields

 

Hey Wouter,

 

I�m trying to define a parameter of type �select� for a field (it�s a non collection type parameter), so I specify the tagged value @andromda.struts.view.field.type with a type of �select� but the code that is generated is uncompilable, it basically says my action form doesn�t implement the backing list for this field.  Is there something else I need to set?

 

Thanks,

 

Chad

Reply via email to