Well Actually I am using JSP to write data into the form bean that is stored in the session. Then have a html form that allows the user to manipulate some of the data in the form-bean before submission.
I am changing the subject because the bulk of the email deals with a different question... Actually this raises a design question that I should have asked earlier - Im starting a separate thread with "Design Question - Struts for Generic Applications". Pratima -----Original Message----- From: Bill Siggelkow [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 5:56 AM To: [EMAIL PROTECTED] Subject: Re: Why no Bean Population tags? Pratima -- it sounds like you are trying to use a JSP page to write data into the session from someplace other than the form. You probably want to put this code someplace else -- like in an Action (or delegate). It is hard for me to guess without more specific information. Gogineni, Pratima wrote: > We have bean:write tags that read bean properties and output to the jsp > page. > I am wondering why we are always forced to set bean properties through one > of the form tags. > > In many cases where there are a lot of common properites to be set it is > easier to set the bulk of the bean properties through bean tags & only > expose the necessary fields through the html form. This also helps in > cleaner pages where you want to do redirects through a hidden page which > sets values into beans in the session. > > I saw the jstl c:set tag but that is not as powerful as the struts bean tags > in terms of dealing with indexed properties. So I have had to write a custom > tag for this. It seems fairly straight forward to do this & hence I am > wondering why the standard struts tag library doesnt contain this. Im > wondering if this violates some design principle in struts. > > Pratima --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
