Laurie, The form is largely handled in two parts. The JSP is interpreted and the form inputs are rendered as properties of a bean. The struts tags uses reflection to get a hold of the values held by the bean. These property names are written out as the names of the form elements. When the form is submitted, the struts servlet uses the property names of the form elements to get a hold of the setter methods in the bean and sets them according to the values of those passed by the form. The servlet maps the action URL to the beans that it has to work against.
So the the taglib is the mechanism to allow the showing of the values, and the servlet is the mechanism that recieves whatever is set by the tags. This is an automatic process. If your form shows the same page straight after, the values will be populated with those that were sent by the form. The servlet is the first thing to run, so you can't really interrupt this process. As for the validation... I don't know. Where I work wrote their own validation mechanism which I have to abide by. Arron. Laurie Harper wrote: >Hi, I'm looking at integrating the struts-html taglib into an existing >web application framework to provide form handling support. I >understand the form rendering process including how form input fields >get populated from the associated bean(s). > >What I'm not clear on is how the submitted data gets back into the bean >when the form is processed or if it needs to be re-displayed. I thought >the idea was that you associated your bean(s) with the form and then >queried that bean in the action that handles the form submission. Do >you have to use the request parameters to retrieve the submitted data? >In that case, how does the validate() method come into effect? > >Sorry if I'm missing something really obvious here... > >L. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
