Here is a problem which _MIGHT_ benefit from the proposal. I am still too much of a newbie to be sure but haven't found any discussion of it in the lists or docs
I'm using container managed security with form authentication. Because of the context path prepending problem, I can't use FormTag for j_security_check but must use HTML <form> instead. This means I can't use the struts-html tags in the form. I have not been able to get login error messages handled in the login page in the way I used to when I depended on programmatic security as per the struts example. I would like my login page to have the same look and feel as the rest of my pages. I have not been able to figure out (yet) how to use tiles for this page (which I use for the rest of my web app) and have been reduced to manually simulating my tiles based layout (no great hassle but annoying). Perhaps with some guru magic all this is possible but I suspect that the HREF attribute might help. Cheers, Alan Craig R. McClanahan writes: > > On Mon, 28 Oct 2002, Taylor, Jason wrote: > > Does anyone oppose the idea of adding an 'href' attribute to FormTag, along > > the lines of the 'href' attribute possessed by the LinkTag, that can be used > > instead of the 'action' to determine where the form is submitted? If so, do > > you have an alternative that allows me to prevent the context path from > > being prepended? If not, I'd be happy to submit a patch. > > > > One of the things you'd give up when doing this is the ability of Struts > to identify the associated form bean. Therefore, it seems like this would > only be of use in constructing a form to be submitted to a non-Struts app > -- and, for that, you can just use a normal HTML <form> element directly. > Am I missing something? > > > -JT > > > > Craig -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
