• Post Reply Bookmark Topic Watch Topic
  • New Topic

J2EE Learning Curve  RSS feed

 
Deependra Tewari
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am new to Java especially to EE. I come from a C, C++ background building standalone apps. In the client-server or enterprise level I've virtually no experience.In J2EE, there are so many things & all of them seem to be important for developing an enterprise app that I'm absolutely confused as to what to begin learning first.

I'm familiar with J2SE. I can also write servlets, Basic JSP (without tags) and basic EJB that can connect to a db using JDBC.

But I've understood that what I know is very basic. I need to do more coding and that requires spending time. It's an investment I'm going to do but in an organized manner.

So should I first go through all the design patterns or should I first go through EJB then servlets and JSP and in the end look at design patterns. What I feel is that design patterns govern the overall app development and hence the required skill-set!

Please advice me so that I may not end up as a gr8 hoch-poch.
 
Tom Fulton
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Personally, I would look at J2EE Design Patterns after getting comfortable with the EJB and Servlet APIs (and the association technologies like JNDI and JTA). There is more than enough to keep you busy for a while...your code will likely be functional but not graceful. Who cares? Then, after you are comfortable with the basic features, and you have a bit of experience under your belt, then J2EE Design Patterns will be helpful.

However, I think it would be useful to know basic Design Patters (sometimes called GoF for "Gang of Four), because they recur so frequently in every environment. I have liked the Head First Design Patterns book very much for this purpose. you should be able to learn GoF patterns at the same time as the EJB/Servlet work.

Even better: if you work at a midsize or larger company, start a Design Patterns study group with 8-12 other people. Meet once every two weeks for lunch, discuss one pattern per meeting, and in a relatively short time (12 months or so) you'll have them all learned.
 
Manuel Palacio
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I wouldn't spend much time with EJB. Focus rather on the Spring Framework's approach to building applications based on the framework. It's more fun and you'll also learn a lot about testing and design patterns.
 
Deependra Tewari
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My guide introduced me to J2EE and now I like it and hate it at the same time !

There are sooooo many things in it that by the time you get the feel of any one thing, the world alrady has something new.

As I finished understanding JDBC (barely able to set-up an use a DataSource of JDBC 3.0) I got a shocker of Hibernate !! :roll:

As I realized there is something called Struts implementing the controller servlet design pattern, I get a new name SPRING framework !! :roll:

Gr8. But right now I think I'll stick to refurbishing my servlets/jsp/ejb basics and start with design patterns alongwith.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!