scope for form beans
Hi, what are the motivations for having a request or session scoped form bean. As far as I could see in the struts source code a request scoped form bean is instantiated newly for every request. What are the reasons for that. Why shouldn't a form bean always exist during the time the session exists? peter DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
button tag
Hi, I have a question about the html: button tag. The discription about the property attribute of that tag is the following: Name of the request parameter that will be included with this submission, set to the specified value.. And additionally the value attribute has the following description: Value of the label to be placed on this button. This value will also be submitted as the value of the specified request parameter. As far as I understand these descriptions I would expect the value of the specified parameter in the HttpServletRequest object. That means when I call the getParameter(String) method with the specified name of that button tag I would expect to retrieve the value specified in the tag. I tried to do this but it didn't work. Am I wrong with my assumption. Peter DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
General design question
Hi, I have a general design question. Assume a web application that represents a use case over several sites. Each of these sites have form fields. Each site has a Next and Previous button except the last an the first which only have either a Next or a Previous button. Additionally there is a navigation bar where you can navigate to each site directly. In general I would appreciate design recommendations for this kind of application. More specifically I have the following questions. - Do I need to have an extention of the org.apache.struts.action.Action class for each site. - If so, how do I manage the handling of the different button events that are coming from a specific site. Peter DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
hidden fields
I have a problem with the html:hidden tag. I tried the following: html:form action=/AnnuityClientInformation method=post html:hidden property=Action value=Hallo/ /html:form I also implemented a FormBean which is associated with the jsp where this form is in. This bean has a getAction() and setAction(String) method. I assumed that the 'Action' property of this FormBean will be set when this form is submitted. Somehow I couldn't manage to make this happen. Am I missing here something or is there a bug in this tag. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]