Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>"learn XYZ in 21 seconds"</p> </blockquote> <p>Better read <a href="http://norvig.com/21-days.html" rel="nofollow">this</a>.</p> <p>You might be trying to bite off more than you can chew here.</p> <p>You need Java - that's fundamental.</p> <p>But you can go a long way with just servlets, JSPs written using JSTL, and JDBC.</p> <p>You don't need Spring right away, but it will help you structure your apps in a good way. I would recommend Spring as an excellent example of well-designed, well-implemented, well-tested code looks like.</p> <p>Hibernate should be at the end of the line. You may not need or want dynamically generated SQL.</p> <p>I agree with the Grails recommendation because it'll ease your entry, but if anything goes wrong you'll be dead in the water. Grails is based on Java, Spring, Hibernate, and Groovy. If you don't know anything about its underpinnings you'll be at its mercy if it fails.</p> <p>UPDATE: </p> <p>Since you've provided more information, I'll add another thought.</p> <blockquote> <p>The goal is to write a full and complex application (I'm working for a global company) over MVC with lots of different patterns, also use of ORM, cache and persistence.</p> </blockquote> <p>Now that we've established that this is a long process, you need to make sure that the global company you'll (hopefully) be invoicing for this work is ready to support it. Do they have the infrastructure, the staff, the knowledge to follow you down this Java EE path? If not, you won't be doing them a service. Prepare them for what you have planned at the same time that you're preparing yourself.</p> <p>Good luck. Maybe we can help you climb that mountain.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload