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/01/28 08:16:44 UTC

DO NOT REPLY [Bug 6061] New: - Need method like validate for multi-page forms

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=6061>.
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=6061

Need method like validate for multi-page forms

           Summary: Need method like validate for multi-page forms
           Product: Struts
           Version: 1.0.1 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Standard Actions
        AssignedTo: struts-dev@jakarta.apache.org
        ReportedBy: brill@users.sourceforge.net


I'm building forms that have multiple pages all pointing at the same form and 
action beans. The action is not called until all the forms have been processed 
and the form bean has all its data. I can send the user to any page in the 
sequence, I just specify a common pageindex property across all the forms. The 
trouble is that the only simple way to get a form to return without adding a 
bunch of code that forces the form processing to do things outside it's scope, 
is to return an error in the validate method(s). (FYI - I'm still debugging 
this, so I'm not positive it will work, and I may have to fall back on 
separate form and action classes for each page).


What is needed is some sort of return method that is separate from the 
validation routine. This could even be built into the process so that you add 
another &lt;struts:html/&gt; element called pageindex or something.

Anyway, it'll be a little late for my current application, but its something I 
could really use in the future, as this is a common problem I have to solve. 
In this case, its important to have all the information that I'm going to try 
and update the databases with, so I can properly process the transaction 
accross multiple tables and/or databases.

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