Home/ Questions/Q 7688043
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T19:50:00+00:00

I am new to JSP/Servlets/MVC and am writing a JSP page (using Servlets and

  • 0

I am new to JSP/Servlets/MVC and am writing a JSP page (using Servlets and MVC pattern) that displays information about recipies, and want the ability for users to “comment” on it too.

So for the Servlet, on doGet(), it grabs all the required info into a Model POJO and forwards the request on to a JSP View for rendering. That is working just fine.

I’d like the “comment” part to be a separate JSP, so on the RecipeView.jsp I can use to separate these views out. So I’ve made that, but am now a little stuck. The form in the CommentOnRecipe.jsp posts to a CommentAction servlet that handles the recording of the comment just fine. So when I reload the Recipe page, I can see the comment I just made.

I’d like to:

  • Reload the page automatically after commenting (no AJAX for now)
  • Block the user from making more than one comment on each Recipe over a 1 day timeframe (via a Cookie). So I store a cookie indicating the product ID whenever the user makes a comment, so we can check this later? How would it work in a MVC context?
  • Show a message to the user that they have already commented on the Recipe when they visit one
    which they have commented on

I’m confused about using beans/including JSPs etc on how to achieve this.

I know in ASP.NET land, it would be a UseControl that I would place on a page, or in ASP.NET MVC, it would be a PartialView of some sort. I’m just confused with the way this works in a JSP/Servlets/MVC context.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    you can use response.sendRedirect() or forward APIs in javax.servlet to redirect to a new page or refresh the same page (redirect to the same page/path so that the beans/data gets refreshed)

    about restricting to one comment per day – yes you can use cookie but the problem is that user might use another browser type (chrome, FF, Safari) and will be able to make multiple comments.
    Ideally you should store the lastCommentTime in the model/persistent store and tie it to the user information – this way your model object can expose an API that checks the last comment time and returns true/false depending on whether user can comment or not.
    You can use this API in your servlet/JSP to show/hide the comment button, for example and also show a message

    • 0