jsp - MVC - controller-to-controller in java EE -


in school, payroll application, professor following logic flow:

  • the default page index.jsp page.
  • when add button clicked, addform.jsp page called , there user can enter data payroll
  • when submit button clicked, addform.jsp page call servlet processes form , add table.
  • say insert statement works , there no problem input data, servlet call add.jsp page. contains input data user entered before, informing user data inserted table, , "list of payroll" link.
  • when "list of payroll" link clicked, servlet called, 1 processing rows in table viewing.
  • finally, resultset containing data table, bound request object, servlet call list.jsp view data in table.

he said how mvc should done.

however, don't when after data inserted, jsp page have created display input data , inform user data inserted. why not go directly list.jsp page , error.jsp page if insert not successful? thought of following wanted:

  • say insert statement works , there no problem input data, servlet call servlet processes data in table.
  • finally, resultset containing data table, bound request object, servlet call list.jsp view data in table.

but not sure if still mvc when call controller when should redirecting view. approach better in terms of being mvc , user friendly or professor's way better?

first of all, teacher isn't using mvc, since half of pages displayed without ever going through controller: index.jsp view displayed directly, , addform.jsp.

whether display result page or going list directly doesn't have mvc. it's functional/user experience choice. going list better, , going detail page of created product better. example, user might want fix error made when creating product. or might want provide more information product, or whatever.

going error page, once again, user experience choice. wouldn't that. instead, redisplay page allowing create product, , display meaningful error messages explaining why product couldn't created , how user should fix data in form.

regarding way implement going list after successful creation, way isn't best way. after successful post, should redirect. known post-redirect-get pattern. has many benefits:

  • simple workflow @ server-side, , isolation of responsibilities
  • allows user refresh page without reposting product
  • allows user bookmark list page , bookmark list page, instead of bookmarking url of servlet handling creation.

of course, same true if want go product details page: should redirect.


Comments

Popular posts from this blog

c# - Validate object ID from GET to POST -

node.js - Custom Model Validator SailsJS -

php - Find a regex to take part of Email -