I currently have a servlet that handles several different HTML forms from
its doPost method.
Currently, I check a hidden form element to determine which form was just
posted then I call
one of a number of private methods on the servlet to process the form.
This is working fine, but there is the possibility I may need to add
additional form processing
and I don't want to continue adding additional methods every time a new form
is added.
The servlet in question is acting as the controller of a HTML wizard used to
build a fairly
complex Javabean used in the application.
Any design ideas on effective ways to decouple the controller from the form
processing would be
appreciated? I have a couple of ideas myself, but I'd like to hear what
others have to say on the
subject.
Grant
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
