If it's for the grade, then use what you already know. No reason to risk the outcome by getting in over your head. However, if you feel you must learn something new in the process I'm afraid there is no right answer to your question. The task at hand should guide the chosen technology. Use what makes most sense, which brings us full circle to my first point.
posted 13 years ago
Thanks for that wise comment. I take it that you are talking from experience! I think I shall play a safe strategy and stick to hibernate/spring/wicket.
Some folks swear by Struts. Some folks swear by JSF. Some folks swear by Stripes. Some folks swear by EJB. Some folks swear by Hibernate. Some folks swear by JDBC. Some folks just swear.
There is no golden hammer. You look at the project requirements and determine which technology makes most sense. Often times you *will* use the same things on many projects. But you should always consider alternatives to make sure you are still being as productive as possible.
I wasn't selected to go to mars. This tiny ad got in ahead of me:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop