<snip>
On Sun, 23 Jan 2005 17:21:08 -0700, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> What do you mean by 'farming' the values?  IIRC this all started when you
> didn't want to pre-define property names.  Could it be that a Mapped
> property in a normal ActionForm would do what you want?  Do you really need
> separate properties for each one, or would putting them all into a single
> Map do just as well?
</snip>

I already use a mapped property in my ActionForm.  My only difficulty
comes when I want to put dynamic property attribute values into Struts
html tags, because the ActionForm requires that I have a pre-existing
getter/setter set for all property attributes.  That is what I have
understood from you can be handled with a LazyValidatorForm. 
Everything else that I do works with Struts 1.2.6 as long as I don't
use LazyValidatorForm.

I want to stress that my ONLY problem is that I want to use a dynamic
variable in <html:select property='<c:out value="${room.value}"/>'
size='1'> in the code shown below.  The property will then have values
like: 147.chat.room3.sound and 147.chat.room4.sound.  What these
values are cannot be predetermined, so I have to be able to get them
either just from normal input type attributes or from some ActionForm
that can handle not having the value preset.


                            <c:forEach
items="${adminForm.stateBaseMap.DATA_3C.list}" var="room">
                              <font color='<c:out
value="${state.banMddlBgClr}"/>'>
                                <html:select property='<c:out
value="${room.value}"/>' size='1'>
                                  <html:options
                                    collection="sound_list"
                                    property="value"
                                    labelProperty="label" />
                                </html:select><br>
                              </font>
                            </c:forEach>

Is this clear?  I have no trouble with Struts 1.2.6 other than finding
a way to do this.  If I use LazyValidatorForm, my prior code is
busted.  Otherwise, everything is okay.  I have no troubles with
commons utils until I use LazyValidatorForm.  However,
LazyValidatorForm does, apparently, what I need.  I think I have to
look more closely at LazyValidatorForm and see what is wrong there. 
Since I have no difficulty "farming" (getting the values) from
ActionForm I don't see why I should have a problem with
LazyValidatorForm using the same code.  I am not trying to get the
values of those parameters particularly related to LazyValidatorForm
at this stage.'

Maybe I should stress that the only change I made in my code was from
"implements ActionForm" to "implements LazyActionForm" and that leads
to all these troubles.


Jack

-- 
------------------------------

"You can lead a horse to water but you cannot make it float on its back."

~Dakota Jack~

"You can't wake a person who is pretending to be asleep."

~Native Proverb~

"Each man is good in His sight. It is not necessary for eagles to be crows."

~Hunkesni (Sitting Bull), Hunkpapa Sioux~

-----------------------------------------------

"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based
on this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to