The first scholar of the Java Web road __java

The road to Java Web development-some tips for getting started
Java is a pleasant thing to do with web development.
You will say I am talking in my sleep, hehe ~ ' Slowly come on ~

-* The following are personal opinions, just a comment, no copyright, for reference only. - * -

First, the beginning, the beginning of everything difficult ah.
Java learning is difficult, because it is too complex, there are many scary (not the language itself) details.
Let's take a look at what we're going through:
1. Expresses
The face of the part, here will be used in the technology and knowledge: JSP,SERVLET,XML,HTML,JAVASCRIPT,CSS, it is best to understand the network base (TCP/IP protocol, etc.).
2. Business logic
The core of the section, where the technology and knowledge will be used: Java bean,xml and so on.
3. The database
The stored part, here will use the technology and knowledge: the knowledge of the database, Jdbc,xml and so on.
4. Deployment
The necessary part, the use of the application server, such as Tomcat, or WebLogic.

It seems enough already. No no no, that's not enough. But if it's getting start. That's enough.

Second, how to start.
The multitude, from where to begin. All right. Now listen to my advice:
1. If you have a smattering of the Java language (pure language). Then go and find Ben thinking java. Do not recommend to see the electronic version Oh. Master
2. Web page, if you do not do page design, you need not delve into, but at least to know the basic use of html,javascript,css it. Know
3. OK, now we can look at the Jsp/servlet. It is not recommended to buy books, at least I do not find any better information than the official Javadoc of Sun. You only need a few related tutorials, below Google, or just at Jr.
(If you have time to suggest reviewing the HTTP protocol.) ）
4. JDBC. If you have written database applications and used ADO, then you should be able to master them quickly.
5. Application Server. My favorite is Tomcat, you can pick one you like, resin is also good. Tutorial. No, they all have very detailed documentation, and the places that need to be configured are full of annotations.

Third, how to progress.
If you have more than 70% mastered the above content, then congratulations, you can go further. Take a deep breath and make sure you have enjoyed the joy of success, and then we begin to practice harder ...
Perhaps you have found a lot of problems in (b) practice, a lot of inconvenience, perhaps you will complain should not waste time, but also to continue your ASP or PHP tour ...
is that really true. No no no, don't forget that we use Java.
1. Problems with the presentation layer
Hey. I know you're looking at hundreds of lines of HTML in the Java language mixed JSP file depressed. Let's think of a way. Space is limited, I only tell you some names, you find the answer yourself they are struts,tapestry,turbine ...
2. Problems with the database
maybe you're smart. You've written some JDBC encapsulation classes or SQL automatic generation tools, but the encapsulation persistence layer is too big, and there are already a lot of off-the-shelf tools, and if you're not doing research, then let's use ready-made. Retrieve them hibernate,jdo.
3. The master only uses Notepad/vim.
Hehe ~ ' Certainly, but this is not the only standard. Some of my friends and I have also written in Emacs, because the development environment is too much.
Some of the following IDE recommended to you, the order of the points Oh ~
A. Eclipse open source, free. The background is IBM, all kinds of plug-ins have everything (part of the charge).
B. IntelliJ idea except for a few plug-ins, any feature is not under Eclipse, unfortunately it is charged.
C. JBuilder Famous, Borland's masterpiece.
4. Design problem
Design mode, learning so long, you should have heard it. It can make a lot of problems solve, Google it.
5. Schema issues
What. Has come to this level. When it comes to architecture, we tend to have only a choice, a look at the Java EE Bar, and its core model.
6. Methodology
What is this thing? Philosophy. Religious. Also provides several keywords: Agile modeling, extreme programming, feature-driven development.
7. Complex issues
The complexity of the problem is often unexpected, and our principle is always to try to use standard, mature technology or solutions.
Don't understand. All right. We now want to implement a full-text search engine, so that you choose whether to use the Apache Lucene or write one yourself.
This aspect of Apache and other open source organizations has a lot of tools and frameworks that we can use.

Well, these are the things I can see right now. Let's work together.

Art is boundless ...