I can't believe it - it works! Look at this : I am currently
(?overengineering) organising my view data in the following way :
TicketTypeForm
| _ property type Vector of "tickettypeChooseViews"
|... |_ each has 1. property type
vector of "multiBox_ids"
2. property type Array of
"selectedMultiBox_ids"
Okay? So now populating them in jsp via :
<logic:iterate id="tickettypeChooseView"
name="TicketTypeForm"
property="tickettypeChooseViews"
type="TickettypeChooseView"
indexId="currentCatEvtIndex"
>
...and later..
<bean:define id='TTForm'
name='tickettypeChooseView' property="tickettypeItem"
type='MtixBaseForm' toScope='request'/>
...and later ..
<logic:iterate id="currentTickettype_id"
name="TTForm"
property="multiBox_ids"
indexId="currentTicketTypeIndex"
>
....finally...
<html:multibox
name='TicketTypeForm' property='<%= "tickettypeChooseView[" +
currentCatEvtIndex + "].tickettypeItem.multiBoxSelected_ids[" +
currentTicketTypeIndex + "]" %>'>
<bean:write
name="currentTickettype_id"/>
</html:multibox>
</logic:iterate>
</logic:iterate>
-> and WOW - they found properly forth and even back. Of course I did
all my reset(mapping, request), beginning from TicketTypeForm's reset
delegating to the reset method of my tickettypeChooseViews.
By the way, my first mistake was, that i used the exposed id TTForm to
populate directly via
<html:multibox name='TTForm'
property='multiBoxSelected_ids'>
<bean:write
name="currentTickettype_id"/>
</html:multibox>
...so they found the way bean -> jsp but were not populated the way html
-> bean. As my learning, for such nested data structures on the way back
always begin at the root.
?!?!? By the way, can anybody assist me in rebuilding this example
properly with "struts nested taglib" - suddenly I think i do some double
work, isn�t it ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
