Beginning Java EE

Question

I know something about Java but completely new to Enterprise Java. I\'m trying my hand with NetBeans 6.1 and GlassFish Application Server. Please guide me to some resources whi

Answer 1

"what java enterprise applications are, how they are different from normal java classes etc"

Well they are normal classes. They are ran by an application server. The "application server" is often just a JVM, but sometimes enhanced or modified or extended by the vendor. But that shouldn't be any concern to you. The application server (ie: JVM) uses a class loader (probably customized by vendor) to load your servlet (any class that implements the HttpServlet interface). Any other classes (not just J2EE classes, but all classes) will be loaded by the class loader. From there on it is your same java code. I hope this gives you the kind of answer you want. Reading J2EE documents (even aimed towards developers) usually entails meaningless buzzwords.

I would recommend that you look over the J2EE Tutorial from Sun. It's free, and goes over the basics that you should know before moving onto a framework (Struts for example). And of course must need to know if you are just going to use just straight J2EE.

You may wish to familiarize yourself with some of this:

• http://java.sun.com/j2ee/1.4/docs/api/
• You may also wish to go over HTTP specification (RFC or elsewhere) as well in case you don't understand how http requests and responses are processed by a standalone webserver.
• http://java.sun.com/j2ee/1.4/docs/tutorial/doc/Overview3.html (web containers in particular)

A couple of helpful facts:

• A JSP is compiled into a servlet. These were created so that your Servlets wouldn't have to be developed using an Output Writer to handle every write to page content (the JSP will be compiled into that for you). ie: out.println("etcetc...")
• the request (HttpServletRequest) object represents the request.
• the response (HttpServletRespone) object will build the response. (both the http headers and content).
• Session and Context objects are also important. The former is for carrying session scoped objects (managed by the app server) and mapped to a jsessionid cookie on the client side (so it knows what client (ie: request) has what objects on the server side). The context object is used for initial settings.
• You will want to go over web containers to fit it all together.