Hi,
It appears that the UI tags all include standard header and footer code that places them within a table within the containing form. This allows validation errors to be nicely formatted above the relevant input. However, the simple structure of this table makes it hard to create forms that are not laid out in its extremely simple manner. For this reason I could not use the UITags in my last application.
I think that if the UITags were simplified to not include this 'layout' functionality they would become much more useful to most real life web applications. I need the ability to define exactly where the error messages will appear on the page. More importantly I need the ability to layout form fields in a pattern other than the simple 'one row per field' that is assumed by the UITags.
I'll assume WebWork 1.3, if you're talking about 2.0 please ignore my reply (as I haven't yet had the chance to try 2.0).
You can redefine the UI tags to your liking, by creating another directory in the template directory of your webapp. For example, in one of our apps we have:
template/xhtml template/sdg
where the sdg directory contains our customized tags. In the JSP pages we use our custom UI tags by adding the attribute template="'sdg'" to the tag.
Hope this helps.
Ing. Sebastiano Pilla, CTO
SDG Engineering s.r.l.
Via della Chiesa Campocroce 4
31021 Campocroce di Mogliano Veneto (TV)
Tel +39-041-5947721
Fax +39-041-5947722
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
