If you're prepared to be patient, I need both of these, and
can work on them but I won't be able to start unitl January
on the development of it.
The AutoBean idea (as an idea) is something I use already
in Cold Fusion, and have done before in PL/SQL.
The client side validator, as I posted before I have a good
JavaScript validation library I can use, and am happy
for it to be included.
"Craig R. McClanahan" wrote:
> The "AutoBean" concept has been requested several times, often in the guise of
> "beans with dynamic properties" so that you don't have to create a form bean
> with individual getters and setters. I'd like to explore this concept in depth
> in Struts 1.1, which will give us time to make sure that a complete and coherent
> set of support for such beans can be included (for example, all the custom tags
> that know how to extract bean properties should now how to extract them from an
> AutoBean, without the page developer having to do anything).
>
> The "Validator" concept is interesting. Besides the server-side format checking
> that is being done here, I would also like to see the option for the form tags
> to generate client-side JavaScript code (if requested) to check as many things
> like this as you can on the client side, to improve the user experience.
