So I was converting my view pages to use velocity instead of WW's tag
library, and I just started on my form pages.  I was replacing the WW
custom form tags with standard html form markup.  I soon realized
that the handy error handling logic that puts the error message next
to the control with the error goes away when I convert to html form
tags.

Is this supposed to happen?  The WW form doc says that you can mix
and match WW form tags with standard form tags...

Yep. The WW form tags contain a bunch of built in behavior that developers may not wish to use. So WW provides a bunch of alternate ways to generate forms:


* Use the provided WW tags. WW1 stores the templates for these tags in /template/xhtml in your webapp directory. WW2 stores these templates in /decorators/xhtml in your classpath.

* Create a template. You can modify these or create your own templates using the template attribute. You can even create your own theme (a set of templates) customized to the needs of your app. See the following link for definitions of template and theme.

http://www.opensymphony.com/webwork/tag-attributes.html

* Use html form tags. However, at this level, you're required to provide all the functionality yourself.

M




-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to