Jump to content

Jakarta EE

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 68.44.67.224 (talk) at 23:55, 8 July 2006 (→Java EE vs. .NET). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Java platform editions

Java Platform, Enterprise Edition or Java EE (formerly known as Java 2 Platform, Enterprise Edition or J2EE up to version 1.4), is a programming platform—part of the Java Platform—for developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. The Java EE platform is defined by a specification. Java EE is also considered informally to be a standard because providers must agree to certain conformance requirements in order to declare their products as Java EE compliant; albeit with no ISO or ECMA standard.

Java EE includes several API specifications, such as JDBC, RMI, e-mail, JMS, web services, XML, etc, and defines how to coordinate them. Java EE also features some specifications unique to Java EE for components. These include Enterprise Java Beans, servlets, portlets (following the Java Portlet specification), JavaServer Pages and several web service technologies. This allows the developer to create an enterprise application that is portable between platforms and scalable, while integrating with legacy technologies. Other added bonuses are for example that the application server can handle the transactions, security, scalability, concurrency and management of the components that are deployed to it, meaning that the developers can concentrate more on the business logic of the components rather than the lower level maintenance tasks.

History

The original J2EE specification was developed by Sun Microsystems. Starting with J2EE 1.3, the specification has been developed under the Java Community Process. JSR 58 specifies J2EE 1.3 and JSR 151 specifies the J2EE 1.4 specification. The Java EE 5 specification was developed under JSR 244 and the final release was made on May 11, 2006.

General APIs

The Java EE APIs includes several technologies that extend the functionality of the base Java SE APIs.

javax.ejb.*

The Enterprise Java Beans API defines a set of APIs that a distributed object container will support in order to provide persistence, remote procedure calls (using RMI or RMI-IIOP), concurrency control, and access control for distributed objects.

javax.servlet

The Servlets API defines a set of APIs between a web container and a servlet that is responsible for processing requests and issuing responses.

javax.servlet.jsp

The javax.servlet.jsp and javax.servlet.jsp.tagext packages define the JavaServer Pages API.

javax.naming

The javax.naming, javax.naming.directory, javax.naming.event, javax.naming.ldap and javax.naming.spi packages define the Java Naming and Directory Interface (JNDI) API.

java.sql, javax.sql

The java.sql and javax.sql packages define the Java Database Connectivity (JDBC) API.

java.transaction.*

These packages define the Java Transaction API (JTA).

javax.xml.*

These packages define the JAXP API.

javax.jms.*

These packages define the Java Message Service (JMS) API.

Low cost development

One of the benefits of Java EE as a platform is that it is possible to get started with little or no cost. The Java EE implementation from Sun Microsystems can be downloaded for free, and there are a great many open source tools available to extend the platform or to simplify development.

Examples of third party open source Java development tools include:

Java EE 5 application server certified

J2EE 1.4 application server certified

Java EE vs. .NET

Arguments about the merits of Java EE vs. Microsoft's .NET abound. One "consensus" is that Java EE is best for multiplatform architectures, whereas .NET should be used for a strictly Microsoft platform (and not to be migrated to for non-Microsoft platform integration).

==================================================================

Totally incorrect assumption: .NET is both cross platform as well as cross language. More than 20 languages support .NET specification till date. .NET specification is an approved ECMA/ISO standard (unlike Java which is still controlled by Sun). Visit http://www.mono-project.com for further details. Mono provides the necessary software to develop and run .NET client and server applications on Linux, Solaris, Mac OS X, Windows, and Unix. While it is true that Microsoft .Net Framework SDK can also be used to develop Windows specific applications, but one can develop strict CLR/CLS/CTS compliant application without using Windows specific or non-CLS features so that they can be truely cross-platform, cross-language and interoperable applications.

Publications

  • Perrone, Paul J. (2003). J2EE Developer's Handbook. Indianapolis, Indiana: Sam's Publishing. ISBN 0-672-32348-6. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)

See also

Examples of Java EE application servers include:

Retrieved from "https://en.wikipedia.org/w/index.php?title=Jakarta_EE&oldid=62796931"