Is that normal that I have to access a webpage in the scure area to get the login-page? How can I access direct the login-page cause I would like to have link on my main-page for login
-----Ursprüngliche Nachricht----- Von: Jon.Ridgway [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 3. Dezember 2001 11:40 An: 'Struts Users Mailing List' Betreff: RE: HTTP form based authentication Hi Shri, I have found the best (only?) approach is not to use a struts html:form tag on your login screen as you are posting to the containers auth mechanism not the struts action servlet, Jon Ridgway www.upco.co.uk -----Original Message----- From: Shri [mailto:[EMAIL PROTECTED]] Sent: 02 December 2001 23:29 To: Struts Users Mailing List Subject: HTTP form based authentication HI all, When we follow HTTP form based authentication, for the form field we write: <form method="POST" action="j_security_check"> ( as per servlet specifications ) Using an action other than ".do" will break the action / action servlet chain... How to make this a part of action chain? Any way of work around for this?? Shri -----Original Message----- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Friday, 30 November 2001 8:19 AM To: Struts Users Mailing List Subject: Re: Hidden Field in a form. Do I use struts taglib or vanilla html? The cleanest thing is to put the ArrayList on the ActionForm. The syntax of the options tag is suboptimal, so you need to expose the property as a bean. <html:select property="namesId"> <bean:define id="names" name="actionForm" property="names" type="java.util.Collection"/> <html:options collection="names" property="value" labelProperty="label"/> </html:select> So, you go through an Action, and have it setup the names list. If there's validation involved, use the same Action as the input path, so the list gets made again. This also makes it much easier to retrieve the list from a database or static class that is on the business tier. David Lauta wrote: > > Wow, > Thanks Ted this is great info. > > I have narrowed my problem down to: > I want to use a <SELECT> Tag on a form and I want the options to be > populated when the form is first displayed. > To do this I need to set an ArrayList of valueLabel pairs in the page Context > > pageContext.setAttribute("names", actionForm.getNames()); > // getNames returns an ArrayList > // each Item in the arrayList has a getValue() and getLabel() accessor. > This works but is coded in the JSP ( tightly coupling the UI with the Model ). > I'm looking for a way to set the attribute outside of the JSP > so that the following will work > > <form:select > property="namesId" > onchange="javascript:submitForm()" > > <form:options collection="names" property="value" labelProperty="label" /> > </form:select> > > In the sequence of events listed below when is the earliest that I can obtain the > pageContext > to call the setAttribute() method on it. I'm guessing that the PageContext of the JSP is > the same as the > ServletContext of the HTTPServlet > > Could my problem be related to I am using the ActionForm instead of the ActionFormBean > class? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>