Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This has been asked in few times in this thread. But sometimes its hard to make it decouple. Let say Im dealing with session, cookie stuff how do I decouple or basically how do I move the existing code out from the JSP? UseBean will be a good alternative. But how to deal with business logic with lot of HTTPServletRequest and HTTPServerletResponse and its related objects used services?
Thank you
Developing web-applications in Java has evolved quite a lot over the past 10 or so years. PHP-style JSP pages may have been ok-ish in 1999 but not today. At very minimum, you should isolate your business-logic in a servlet and only have your rendering/view in the JSP. That is just the bare-minimum to pass some form of basic level of hygiene. If you are doing any sort of new development or even refactoring, you should look into a more refined MVC/MVP framework. Spring is a good candidate. Maybe not the “coolest” but definitely established and well-known. The tutorial Andrea mentioned is a good place to start. And don’t get too nervous about things like “how does it make sure the right request and session is used” – that is what spring-mvc does, it’s the core functionality. Go through the tutorials, try it out and then dig deeper to understand what is happening under the hood and how you can customize the behavior to fit your needs.