Hello martin,
Thursday, January 11, 2001, 10:50:00 PM, you wrote:
mctc> Something I am working on at the moment is a very simple utility that
mctc> generates a form bean from an XML definition. The goal is simply to reduce
mctc> typing in generating beans - as Roger mentioned, it is kinda tedious. I'm
mctc> using something like this to specify a bean:
mctc> <form-bean name="AddressForm" validate="true">
mctc> <property name="street"/>
mctc> <property name="city" allowEmpty="false"
mctc> errorMessage="error.city.required"/>
mctc> <property name="zip" allowEmpty="false" errorMessage="error.zip.required"/>
mctc> </form-bean>
mctc> Pretty simplistic stuff, but it meets my needs right now. If this would be
mctc> of interest to people (and if my company allows it), I can make it
mctc> available when I'm done.
mctc> Also, if people have ideas on what it might do differently, or what else it
mctc> might do, I'd be interested in hearing them. And if anyone has a copy of
mctc> the messages from Mark Wutka mentioned in the Struts 1.1 TODO list, I'd
mctc> appreciate it if they could forward them to me.
Good idea. I think global errorMessage for missing properties can be
defined. And add type as attribute for property. And add errorMessage
for convertion error with property. And add global errorMessage for
properties of some type.... 8)
--
Best regards,
Oleg mailto:[EMAIL PROTECTED]
