Rick Reumann wrote:
As I side I really don't like Map backed ActionForms (I used to love
them:) for the same reason that I don't like DynaForms (basically a
Map form). The potential for problems later setting the properties is
what bothers me. There isn't any compile time safety. Nothing would
Bill Siggelkow wrote:
Michael McGrady wrote:
Rick Reumann correctly pointed out that I just need to use map.test
rather than value(test). Thanks.
True, map.test will work; I was answering the original question about
why value(test) did not work.
---
Michael McGrady wrote:
Rick Reumann correctly pointed out that I just need to use map.test
rather than value(test). Thanks.
True, map.test will work; I was answering the original question about
why value(test) did not work.
-
Bill Siggelkow wrote:
Michael, for a map-backed property to work with the
property="value(key)" syntax the key must be defined as a String; the
methods must follow the pattern:
public Object getFoo(String key) {…}
public void setFoo(String key, Object value) {…}
Try that out and let me know if i
Michael, for a map-backed property to work with the
property="value(key)" syntax the key must be defined as a String; the
methods must follow the pattern:
public Object getFoo(String key) {…}
public void setFoo(String key, Object value) {…}
Try that out and let me know if it works for you.
Bill
As I side I really don't like Map backed ActionForms (I used to love
them:) for the same reason that I don't like DynaForms (basically a Map
form). The potential for problems later setting the properties is what
bothers me. There isn't any compile time safety. Nothing would prevent
you in your
Michael McGrady wrote:
Yet, when I put setValue("test","TEST") into the session, I get the
following exception from the attempted use of :
"No getter method for property value(test) of bean formName"
try: property="map.test"
that should call getMap and then retrieve the value
--
Rick
7 matches
Mail list logo
