The Java 2 SDK, Enterprise Edition 1.4 (J2EE 1.4 SDK) is a complete package for developing and deploying J2EE 1.4 applications. The J2EE 1.4 SDK contains the Sun Java System Application Server Platform Edition 8, the J2SE 1.4.2 SDK, J2EE 1.4 platform API documentation, and a slew of samples to help developers learn about the J2EE platform and technologies and prototype J2EE applications. The J2EE 1.4 SDK is for both development and deployment.

Yes. Any product conforming to the J2EE 1.3 or later specifications can be used to run this benchmark. CTS certification ensures that the application server being tested is a J2EE technology-based application server and not a benchmark-special application server that is crafted specifically for SPECjAppServer2004. The CTS certification is validated by Sun Microsystems, Inc.

Tomcat is based on the original implementation of the JavaServer Pages (JSP) and Java Servlet specifications, which was donated by Sun to the Apache Software Foundation in 1999. Sun continues to participate in development of Tomcat at Apache, focusing on keeping Tomcat current with new versions of the specifications coming out of the Java Community Source Process. Sun adapts and integrates the then-current Tomcat source code into new releases of the J2EE SDK.

April 26, 2004. See the press release at http://www.sun.com/smi/Press/sunflash/2004-04/sunflash.20040426.1.xml.

The J2EE 1.4 features complete Web services support through the new JAX-RPC 1.1 API, which supports service endpoints based on Servlets and enterprise beans. JAX-RPC 1.1 provides interoperability with Web services based on the WSDL and SOAP protocols. The J2EE 1.4 platform also supports the Web Services for J2EE specification (JSR 921), which defines deployment requirements for Web services and utilizes the JAX-RPC programming model. In addition to numerous Web services APIs, J2EE 1.

No. Although the tutorial used to rely on the J2EE SDK, we converted it to work on the Sun ONE platform. You'll find it much easier to develop J2EE applications and Web services with the Sun ONE software.

A J2EE licensee has signed a commercial distribution license for J2EE. That means the licensee has the compatibility tests and has made a commitment to compatibility. It does not mean the licensees products are necessarily compatible yet. Look for the J2EE brand which signifies that the specific branded product has passed the Compatibility Test Suite (CTS) and is compatible.

The J2EE 1.2.x Reference Implementation did not include an implementation of the JMS API. It included only the interfaces. The JMS Reference Implementation is available as part of J2EE 1.3 and you can run the sample programs with the J2EE 1.3 server. See the JMS Tutorial for information on running simple JMS client programs with the J2EE 1.3 server. Please see Java Message Service API Licensees for a list of vendors that provide implementations of the JMS API.

Complete Web services support. The J2EE platform provides a framework for developing and deploying web services on the Java platform. The Java API for XML-based RPC (JAX-RPC) enables Java technology developers to develop SOAP based interoperable and portable web services. Developers use the standard JAX-RPC programming model to develop SOAP based web service clients and endpoints. A web service endpoint is described using a Web Services Description Language (WSDL) document.

The primary technologies in the J2EE platform are: Java API for XML-Based RPC (JAX-RPC), JavaServer Pages, Java Servlets, Enterprise JavaBeans components, 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. What's new in the J2EE 1.

For more information about the J2EE platform and how to get the specification, see http://java.sun.com/j2ee/. The most effective way to learn about the J2EE platform and what's new in the J2EE 1.4 platform is to get hands on experience with the APIs by using the J2EE 1.4 SDK. The J2EE 1.4 SDK provides a J2EE 1.4 compatible application server as the foundation to develop and deploy Web services enabled, multi-tier enterprise applications. You can download the J2EE 1.4 SDK from http://java.sun.

ISVs need the J2EE platform because it gives them a blueprint for providing a complete enterprise computing solution on the Java platform.

Yes. The J2EE Compatibility Test Suite (CTS) is available for the J2EE platform. The J2EE CTS contains over 5,000 tests for J2EE 1.4 and will contain more for later versions. This test suite tests compatibility by performing specific application functions and checking results. For example, to test the JDBC call to insert a row in a database, an EJB component makes a call to insert a row and then a call is made to check that the row was inserted.

J2EE is an environment for developing and deploying enterprise applications. The J2EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multi tiered, and web-based applications.

The SDK is the Software Development Kit. This together with the tutorial allows you to create your own Rbots level. This could be a brand new level you have created or an old level you wish to convert. Either way, the Rbot SDK is what you need.

J2EE applications that are written to the J2EE 1.3 specification will run in a J2EE 1.4 implementation. Backwards compatibility is a requirement of the specification.

Most of them are band names, there are very many gothic bands with quite long names, these are normally abbreviated. Some common ones are as follows. The goth code is simply a method by which one can very concisely describe oneself. For more information see -Synic-'s homepage at http://www.omen.com.au/~synic/code/index.

The J2EE 1.4 specification is final and you can use the J2EE 1.4 SDK to deploy applications today. However, for improved reliability,scability, and performance, it is recommended that you deploy your applications on J2EE 1.4 commercial implementations that will be available early in 2004. If you want to deploy your application before 2004, and reliability,scability, and performance are critical, you should consider using a high performance application server that supports J2EE v1.

Square jars were considered a design improvement because a homemaker could stack more jars together in less space thus allowing a family to put up more food in their small cellars or cupboards. Square Jars were made for the Smalley Fruit Jar Co. Boston, Mass in the late 1890s. Other square jars date from the 20s, 30s and later. The value of square shaped jars tends to be higher than round as it seems that fewer square jars were made.

A#1.4: The GNO documentation specifies that the minimum requirement is an Apple IIGS with 1.25 MB of memory and a 3.5" disk drive. Realistically (especially with all the third-party add-ons), a hard drive (or other large mass storage device) should be considered a necessity. An accelerator and additional memory is recommended. There is not an official "minimum disk space" requirement as yet. When this information becomes available, it will be added to this FAQ.

JSP: It is possible to use AspectJ to affect code in JSPs by precompiling them into Java sources and compiling these with ajc. This can be used, e.g., to customize displays by turning on and off custom JSP taglibs. The mapping from a given jsp source to java package and class name is not standardized, which means doing this imposes dependencies on specific container versions. EJB: AspectJ supports a wide variety of aspects for EJBs.

The Java 2 Platform, Enterprise Edition (J2EE) is a set of coordinated specifications and practices that together enable solutions for developing, deploying, and managing multi-tier server-centric applications. Building on the Java 2 Platform, Standard Edition (J2SE), the J2EE platform adds the capabilities necessary to provide a complete, stable, secure, and fast Java platform to the enterprise level.

There are numerous choices of tools available for developing Java and J2EE applications. You can download the Open Source NetBeans IDE for free at http://netbeans.org. Many of the J2EE compatible vendors offer tools that support any J2EE compatible application server.

JBI does not require J2EE (or Java EE). Certain JBI components may require a J2EE JBI implementation, in order to access technologies such as JTA. The Open-ESB project requires J2EE, and runs within a number of J2EE application servers.

J2EE modules are components that may be individually or collectively (by way of an EAR) deployed into a J2EE Server. They include: EARs (.ear), EJBs (ejb-jar), RARs (.rar), and WARs (.war).

J2EE™ stands for Java 2 Platform, Enterprise Edition. It is a set of open software standards designed to simplify application development for large enterprises. Learn more about J2EE™ at http://java.sun.com/j2ee/.

AquaPDF will work with any standards-based J2EE container such as WebLogic, WebSphere, JBoss and others.

ECperf is used for benchmarking J2EE application servers. It consists of a Specification and a benchmarking kit which is designed specifically to test...