J2EE - FAQ
- 1. What is Java 2 Enterprise Edition (J2EE)?
- 2. Of what technologies does J2EE comprise?
- 3. What tools can be used to build J2EE applications?
- 4. Can applications written for J2EE 1.3 run on a J2EE 1.4 Application Server?
1. What are the goals of performance tuning?
According to Sun Microsystems, J2EE is a coordinated set of specifications and practices that together enable solutions for developing, deploying and managing multi-tier server-centric applications.
2. How often do I need to tune?
The primary technologies in the J2EE platform are:
Java API for XML-Based RPC (JAX-RPC), JavaServer Pages (JSP), Java Servlets, Enterprise JavaBeans components (EJB), J2EE Connector Architecture, J2EE Management Model, J2EE Deployment API, Java Management Extensions (JMX), J2EE Authorization Contract for Containers, Java API for XML Registries (JAXR), Java Message Service (JMS), Java Naming and Directory Interface (JNDI), Java Transaction API (JTA), CORBA, and JDBC data access API. The iTrain course focuses on the flagship EJB, JSP and Servlet models, as well as providing tuition on the inter-container plumbing involved in building J2EE applications.3. Do I need to upgrade my Oracle database?
There are a multitude of established Java tools for developing and deploying both Java and J2EE applications. It may be that you are already tied to a particular vendor, and so are limited to a particular IDE (Integrated Development Environment), there are also a number of open source alternatives. Amongst the most prevalent are:
- Oracle JDeveloper
- Sun NetBeans
- Eclipse
- IntelliJ
- IBM WebSphere Application Developer (WSAD)
There is also a vast choice of J2EE-compliant Application Servers, for deployment purposes.
4. Has the rule based optimizer been made extinct?
J2EE applications written to the J2EE 1.3 specification will run in a J2EE 1.4 implementation. Backwards compatibility is a requirement of the specification, so your application is compatible, but does not make best use of the upgraded environment.
