Would it be better to have something like this: <ww:field name="foo.bar" label="'Bar'" />
instead of <ww:text name="foo.bar" label="'Bar'" /> Consider: the rendering engine can see that the field is a String, so it can generally figure out the rendering type. Maybe String isn't a brilliant idea - maybe there's a possibility of creating new types in WebWork such that the form can look at the type and say "Gee, this is supposed to be a textarea, let's render it that way," or "Gee, this is a numeric type, integral, let's generate an input field that doesn't allow non-numerics or decimal points," etc. No, I don't have any code to show off for this, nor am I convinced this is a "solution," and in fact, I'm not even sure there's a problem... just trying to think in terms of how a user might use this, without having to know the destination types. Imagine: a Phone type, or a ZIP, or a State... all with custom renderers that don't require anything special on the front end... just a reference to the field in question. ------------------------------------------------------------------- Joseph B. Ottinger http://enigmastation.com IT Consultant [EMAIL PROTECTED] J2EE Editor - Java Developer's Journal [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
