Understanding J2EE

[Ray]

Hi,

I am a java developer and have been reading up on J2EE lately and I
learned that J2EE is a container of various API components such as
Servlets, JSP, JDBC, etc.

I am already an experienced web application developer and I've used
these components when developing web applications using MVC pattern.

I used servlets as a controller for all web requests. All views are
contained in JSPs and backened classes to establish connection pooling
to the database.

My question is: when is a J2EE a J2EE application? I am having problem
understanding what is considered a J2EE application. What issues does
it resolve?

I've read that it is for building distributed application. Using my
current knowledge of Servlets, JSP, JDBC, Javabeans, etc. I can build
a 'distributed' application without using J2EE (what I mean is w/o
using EJBs, the deploytool, etc.), just build my own classes using
J2EE APIs directly (raw sockets and threads).

So does using J2EE means conforming to a design pattern by using the
Remote, Home interface, etc.?

Thanks,

-Ray

 

[J. Doe]

My question is: when is a J2EE a J2EE application?

How long is a piece of string? ;o)

If you are using servlets and JSPs you are already using a subset of the
J2EE. A J2EE application that only uses the web tier is still a J2EE
application.

If you are interested in learning some more of the J2EE toolset, I recommend
'Proffesional Java Server Programming' and 'J2EE Design and Development'
(both published by wrox). Milage may vary, but these are two books that are
always very close at hand when I am working on a project.