Rick Reumann wrote the following on 7/14/2005 4:26 PM:
Rick Reumann wrote the following on 7/14/2005 4:20 PM:
From the FAQ I'm going to try this in my ActionForm..
public Object getStringMapped(String key) {
return map.get(key);
}
public void setStringMapped(String key, Object value) {
map.put(key, value);
}
When in doubt look at the docs:)
The above worked fine..and then...
<html:textarea property='metadataMapped(1).metadata' rows="10" cols="40" />
In relation to the above, I'm curious what is going on behind the scenes
(yea too lazy to look it up:), because I'm curious why the ActionForm
doesn't behave like a regular POJO with JSTL.
For example... using JSTL and my POJO I'm doing this ..
<c:when test="${empty
tierMaintenanceForm.metadataObjectsMap['2'].metadataTypeID}">
YET, when I have to use this property in my form I need to create an
extra getter "getMetadataMapped" and the property becomes...
<html:text property='metadataMapped(2).metadataTypeID'/>
To me, this is very confusing. Why doesn't the html:property tag perform
the same kind of logic as JSTL does? I would think I should be able to
just do...
<html:text property="metadataObjectsMap['2'].metadataTypeID}">
and not need to create a new accessor method name and the odd syntax (x) ?
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
