Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Should I do more JavaSE before jumping to JavaEE?

I'm almost finished with the book "Head First Java". The reason I'm studying this is I'm hoping to get a job developing with JavaEE someday. Now I'm thinking, should I go ahead and study EE (moving on to Head First Servlets and JSP) or should I spend more time with SE? Would it help? I'll go on and say directly that I want to learn EE in the quickest yet the most optimum time needed (a balanced ind of way). Any advice?

Thanks in advance!

like image 420
ajushi Avatar asked Dec 31 '08 01:12

ajushi


2 Answers

To me its fine to go with JavaEE, as you already did adequate of SE. And certainly hanging out in programming forums will teach you now and then things which are still hidden from you. Believe me there would be many. Anyhow, I am having few advices for you, which will help you down the road.

  • Its better to have a very good command on Java Collection API
  • Another important is to know Java Threading Mechanism and related classes
  • Effective Java is a must read for any Java developer. So go and read it
  • Don't jump into any framework prior practicing plain Servlet and JSP, adequately
  • To know major design patterns is a must
like image 181
Adeel Ansari Avatar answered Nov 09 '22 09:11

Adeel Ansari


Knowledge is never a bad thing, so more SE is recommended.

But there's nothing wrong with getting your feet wet with EE now. Start with servlets, JSPs, and JDBC. You can do lots of useful things with just these, and it's fair to call it EE.

If you do write JSPs, just make sure that you do it the right way - using JSTL, the JSP Standard Tag Library. No scriptlet code.

like image 2
duffymo Avatar answered Nov 09 '22 07:11

duffymo