You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2002/02/27 16:03:17 UTC

DO NOT REPLY [Bug 6686] - make "action" attribute of html:form tag optional w/default = URL launching it

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6686>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6686

make "action" attribute of html:form tag optional w/default = URL launching it





------- Additional Comments From jmitchtx@yahoo.com  2002-02-27 15:03 -------
What to do with workflow parameter?

How do you plan to handle the submitted form (html) fields (if any) from the 
original page (pre-login) so that they may be re-submitted to the necessary 
action class?

Should the login page:
   1. Write them as hidden (html) fields?
      If so, how to do you handle duplicate fields?
   2. Append them as querystring parameters on the form action(e.g. <form 
action="/doAction?addMe=here&me=too">)
      If so, how to do you handle duplicate fields?

Should the workflow be structured such that the user is never allowed to enter 
(html) form data whose resulting submittal might require authentication?

Would it not be desired to notify the user ahead of time that some action 
requires login?

I am very interested to see how this one turns out.  I have a few suggestions 
if anyone is interested in hearing them.

James Mitchell
Software Engineer
Open-Tools.Org

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>