See http://community.9cbs.net/expert/topic/3105/3105789.xml?temp=4.095095e-02
Arias (eternal way), feel good, turn it down
J2EE learning process
Here I talk about me in learning J2EE processes and talk about the experience and lessons of receipts in this process. In order to be less bent less. Java has developed to now, according to application scores, three major blocks: J2SE, J2ME and J2EE. These three are complementary, the application range is different. J2se is the standard version of Java2, mainly for desktop applications. J2ME is primarily applied to embedding is system development, such as mobile phones and PDA programming; J2EE is a java2 enterprise version, mainly for distributed network programs, Such as e-commerce websites and ERP systems.
First study J2SE To learn J2EE, learn J2SE first, just start learning J2SE first recommend not use IDE, then gradually transition to the use of IDE, after all, use it easy. Learn J2SE Recommend two books, "Java2 Core Technology, Chapter 2", "Java Programming Thought", "Java Mode". Among them, "Java Programming Thoughts" should be studied and intensive. This period of time is basic skill, the time will be very long, or it may be short, it depends on the level of the learner.
Don't be entangled in the process of learning Java and J2EE, you will encounter the five-flowers of IDE, don't be confused by them, learn Java, to learn language itself, don't care too much about the additional features of IDE, Java programming in different IDE The conversion between the conversions is easy, and the function of too much Ide is easy to delay the understanding of the language itself. The current popular IDE has JBuilder, Eclipse, and Eclipse to enhance WSAD. It is possible to use one of them, it is recommended to start J2EE from Eclipse. Because JBuilder is more suitable for writing a J2SE program.
Select and Learn Server Use Configuration When you have J2SE and IDE experience, you can start J2EE's learning, web server: Tomcat, do not doubt, Tomcat is preferred for learning web services. The application server currently has three main: JBoss, WebLogic, WebSphere. There are many projects to start using jboss, and there are a lot of companies to start doing WebSphere or WebLogic transplantation to the JBoss application server (cost savings), what to say is, learning Tomcat and JBoss I think it is preferred, and it is the easiest to get started. Learning Server Use the configuration to ask questions about experienced people (with conditional words), because they can solve the problem, you can get online to explore it. You should have two days (I have to do this stupid), we should Put the main time in learning principles and theory, a particular technology uses to replace a person's knowledge and learning.
Learning Web Knowledge If you are doing an e-commerce website, you may have to act as a few characters, this is you still study: HTML, you may have to use Dreamwave and other IDEs. JavaScript, learn simple data verification, data linkage display, etc.
J2EEAPI Learning learning J2EEAPI and learning server should be an iterative process. First learn JSP and servlet programming, a lot of books, I have established two "JSP Design" and "Java Servlet Programming" of Oreilly, and OREILLY is always excellent, I have to admire. Learning a JDBC database programming, most of the J2EE project is a MIS system, and the access database is the core. This should belong to J2SE learning, here to take it out. Learning JNDI API, it can be combined with learning EJB. Learn the EJB API, the recommendation "Jing EJB" has passed the above learning, probably can deal with the general application. Some people say that SUN's "J2EE Tutorial" is studying all the way, of course, can be. Learning EJB design patterns and see code (most important) design mode is practicing internal work, its importance can be said, if you don't use the design mode, you will write a bunch of rubbish in the use of EJBs, there is slow and slow A bunch of bugs, the result is better not to implement EJB (EJB is not equal to J2EE) No matter what language, you should look at a lot of code, you see the amount of code is less than a certain amount, it is a lot of open source projects that are not good for J2EE. As a textbook: JIVE Forum PetStore Sun Dune Sun, etc., study one and use it to use it in your own project.
J2EE Other Learning When you gradually understand J2EE, you have to pay attention to some of the technologies in the current field. J2EE is a hundred hundred people standing. Everyone is here to propose their own solutions, such as Structs, Hiberate, OFBIZ, etc. Wait, learn these things for your projects and goals, pre-supplement that there is no taste, but don't involve too deep, after all, the principle and theory are the most important thing.
Common J2EEAPIJAVASERVER 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 Message Service (JMS) 1.0 Java Name Directory Interface (JNDI) 1.2 Java Transaction API (JTA) 1.0 JavaMail API 1.2 JavaBeans Activation Architecture (JAF) 1.0 J2EE Connector Architecture (JCA) 1.0 Java Authentication and Authorization Services (JAAS) 1.0 Learning Some APIs The above API should be fixed by your project, understand all them are good The above confirmed a word, Java language itself is not difficult, but there are too many technologies, so learn Java is very hard. Recalling, basically every beginner, may ask someone to ask others when just studying Java, which method do you know (API)? Oh, no one, only hand ripe.
