A word of caution - Commons BeanUtils[1] handles Maps and
JavaBeans/DynaBeans differently and doing this may change how the
ActionForm is populated - for simple properties it would probably be
fine, but I'm not sure that indexed properties would work the same
way.
This related bug may be of inter
Here's a better solution:
Extend LazyValidatorForm to implement java.util.Map (perhaps
BeanValidatorForm,
which LazyValidatorForm extends from, should do this?)
Then you could access ${myForm.myProperty} in the JSTL.
Lance Semmens wrote:
Use LazyDynaForm.getMap()
eg ${myForm.map.myProperty}
Use LazyDynaForm.getMap()
eg ${myForm.map.myProperty}
Scott Van Wart wrote:
I have a class MyForm extends LazyValidatorForm, mapped with name
myForm to myAction:
${myForm.myProperty}
The EL fails with a complaint about accessing myProperty of bean
myForm (since there's no getMyProperty(
Niall Pemberton wrote:
You can get a reference to the Map underlying the LazyValidatorForm
${myForm.map.myProperty}
Excellent, thanks!
- Scott
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMA
You can get a reference to the Map underlying the LazyValidatorForm
${myForm.map.myProperty}
Niall
On 6/22/06, Scott Van Wart <[EMAIL PROTECTED]> wrote:
I have a class MyForm extends LazyValidatorForm, mapped with name myForm
to myAction:
${myForm.myProperty}
The EL fails with a compla
I have a class MyForm extends LazyValidatorForm, mapped with name myForm
to myAction:
${myForm.myProperty}
The EL fails with a complaint about accessing myProperty of bean myForm
(since there's no getMyProperty() accessor). How can I access
properties with EL?
I have
value="${myFor
6 matches
Mail list logo
