Wesley said:
It is a little more complicated.
A J2EE server is a container. The container provides certain services,
such as transaction management, security, persistence, logging etc.
The classes that you would find in the 'j2ee.jar' are classes that
provide the 'container contract'. That is, the mechanism by which the
application server provides these services to your application. The
application server knows about j2ee.jar and your application knows about
j2ee.jar, this is the mechanism by which the application server and your
deployed components interact.
To be honest, what you are asking is a massive question and takes some
time (and entire books) to cover completely. I would suggest that if you
have an interest in the subject, you go through the sun J2EE tutorial or
pick up a J2EE book. Most will explain it far better than I do
Hi, i got a quick J2EE specification here
Quick reference: primary J2EE 1.4 specifications
* Java Servlet Specification 2.4
* JavaServer Pages Specification 2.0
* Enterprise JavaBeans Specification 2.1
* Enterprise JavaBeans to CORBA Mapping 1.1
* RMI over IIOP
* Java IDL API
* Web Services for J2EE, Version 1.1
* SOAP with Attachments API for Java Specification 1.2
* Java API for XML Processing Specification 1.2
* Java API for XML Registries Specification 1.0
* Java API for XML-based RPC Specification 1.1
* JDBC Specifications, 3.0, 2.1, and Optional Package API (2.0)
* Java Connector Architecture (JCA) 1.5
* Java Message Service Specification 1.1
* JavaMail API Specification 1.3
* Java Authorization Contract for Containers 1.0
* Java Naming and Directory Interface Specification 1.2.1
* Java Transaction API Specification 1.0.1B
* Java Transaction Service Specification 1.0
* JavaBeans Activation Framework Specification 1.0.2
from
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websph