Java predecessors: Learning the experience and lessons learned from the EE process I'm here to talk about My Learning the Java EE process and the lessons learned in this process. So that later people less detours.
Java development to now, according to the application to divide into three major chunks: J2se,j2me and Java EE. These three blocks complement each other and are used in different ranges.
J2SE is the standard version of JAVA2, mainly used for desktop application software programming;
J2ME is mainly used in embedded system development, such as mobile phone and PDA programming;
Java EE is Java2 's Enterprise Edition, mainly used for the development of distributed network programs, such as e-commerce websites and ERP systems.
Learn J2SE First
To learn the J2SE to learn the first, just start learning J2SE first recommended not to use the IDE, and then gradually transition to the use of IDE development, after all, with it convenient. Study J2SE recommended two books, "JAVA2 core technology One or two volumes", "Java Programming Ideas", "Java mode". One of the "Java Programming ideas" to study, intensive reading. This period of time is basic learning, time will be very long, it may be very short, it depends on the level of learners themselves.
Don't get tangled up by the IDE
In the course of learning Java and EE, you will encounter a variety of Ides, do not confuse them, learn Java, to learn the language itself, do not care too much about the IDE's additional functions, Java programming between the different Ides of the conversion is very easy, Too much attention to the IDE's function is likely to delay the understanding of the language itself. The current popular IDE has Jbuilder,eclipse and Eclipse's enhanced version of Wsad. Use one of the best, and recommend the Java EE from eclipse. Because JBuilder is more suitable for writing J2SE programs.
Select and learn server usage configuration
When you have J2SE and IDE experience, you can start the Java EE Learning, Web server: Tomcat, needless to know, Tomcat is the first choice for learning Web services. and the application server currently has three main: JBoss, WebLogic, WebSphere. There are a lot of projects that start with JBoss, and a lot of companies are starting to migrate WebSphere or WebLogic to JBoss application servers (cost savings), and here's to say, learning Tomcat and JBoss I think is the first choice and the easiest to get started with. Learning Server Use configuration It's best to ask experienced people (conditionally), because they may be able to solve the problem in a word, you may have to explore the internet for a day or two (I have done such a foolish thing), we should put the main time on the principle of learning and theory, The use of a particular technology can never replace a person's knowledge and learning.
Learn Web Knowledge
If you are doing e-commerce sites and so on, you may want to play several roles, which is what you also have to learn:
HTML, you may want to use the IDE such as Dreamwave.
Javascript, learn simple data validation, data linkage display, etc.
J2EEAPI Learning
Learning J2eeapi and learning servers should be an iterative process.
First learn JSP and servlet programming, this aspect of the book a lot, I set up to see OReilly Company's two "JSP design" and "Java servlet Programming", oreilly out of the book is always that excellent, have to admire.
Learning JDBC Database programming, the EE project is mostly MIS system, access to the database is the core. This should belong to J2SE study, here take out to emphasize.
Learn the Jndi API, which can be combined with learning EJBs.
Learn EJB API, recommended book "Proficient in EJB"
Through the above study, probably can deal with the general application.
Some people say follow Sun's "Java Tutorial" to learn all the way down, of course.
Learn the EJB design pattern and see the code (most important)
The design pattern is to practice the internal strength, its importance can say so, if you do not use the design pattern, you will write a bunch of garbage using EJB, slow is a bunch of bugs, the result is not as good as EJB implementation (EJB is not equal to the Java EE)
No matter what language to learn, you should look at a lot of code, you see the amount of code is not a certain amount, is not good at the Java EE
There are many open source projects that can be used as teaching materials:
Jive Forum
Petstore Sun Ltd.
Dune Sun Ltd.
Wait, read one, and use it in your own project.
Other learning from EE
As you begin to understand the depth of the Java EE, you have to start to focus on some of the technical changes in the current field, and EE is a field of contention, where everyone presents their own solutions, such as structs,hiberate,ofbiz, etc. Learning these things depends on your project and your goals, but it doesn't have to be too deep, after all, learning principles and theories are the most important thing.
Current Common J2eeapi
JavaServer Pages (JSP) technology 1.2
Java Servlet Technology 2.3
JDBC API 2.0
Java XML processing API (JAXP) 1.1
Enterprise JavaBeans Technology 2.0
Java Messaging Service (JMS) 1.0
Java named Directory Interface (JNDI) 1.2
Java Transaction API (JTA) 1.0
JavaMail API 1.2
JavaBeans activation Architecture (JAF) 1.0
Java EE Connector Architecture (JCA) 1.0
Java Authentication and Authorization Service (JAAS) 1.0
Learning some of the above APIs depends on your project and it's good to know all of them.
The above confirms that everyone said a word, the Java language itself is not difficult to learn, but the technology is too much, so learning Java is very laborious. In retrospect, basically every beginner, in just learning Java may ask others such a word, how do you know which method (API) in which package? Oh, without him, only hand-cooked.
Java predecessors: Learning about the experience and lessons learned in the EE process
