Appendix B New Features in EAServer Version 3.6

J2EE platform support

Sun has specified the Java 2 Enterprise Edition (J2EE) platform as a standard architecture for deploying middle-tier business logic implemented in Java and HTML. For detailed information on J2EE, please visit this URL on Sun's Web site:

http://java.sun.com/j2ee/

Enterprise JavaBean enhancements

Jaguar 3.6 implements version 1.1 of the Enterprise JavaBeans specification. The EJB 1.1 model is not software compatible with EJB 1.0. Jaguar supports both versions for backward compatibility with Jaguar version 3.5 and other EJB 1.0 servers, but you must configure the EJB version in the component properties.

See the following chapters in the Jaguar CTS Programmer's Guide for more information on EJB components:

Chapter 7, "Enterprise JavaBeans Overview"
Chapter 8, "Creating Enterprise JavaBean Components"
Chapter 9, "Creating Enterprise JavaBean Clients"
Chapter 10, "Jaguar EJB Interoperability"

Java servlet enhancements

Jaguar 3.6 implements version 2.2 of the Java Servlet Specification, which includes many new features such as request dispatching, response buffering, and integration with the Web application model for standardized configuration and deployment. See these chapters in the Jaguar CTS Programmer's Guide for more information:

Chapter 23, "Creating Java Servlets"
Chapter 22, "Creating Web Applications"

JavaServer Pages

A JavaServer Page (JSP) is an HTML file that contains snippets of Java code and JSP directives that produce dynamic content. The JSP programming model allows you to accomplish most of what the Java servlet model can, but is simpler and easier to learn. Jaguar implements version 1.1 of the JSP specification. Jaguar also implements the Web application model specified by the J2EE and Servlet 2.2 specifications, allowing you to configure and deploy a JSP as part of a Web application. See these chapters in the Jaguar CTS Programmer's Guide for more information:

Chapter 24, "JavaServer Pages"
Chapter 22, "Creating Web Applications"

Web application support

A Web application is a unit of deployment for related Web content, JavaServer Pages (JSPs), and Java servlets. The Web application contains static files, servlet and JSP implementation classes, and a deployment descriptor that describes how the files, servlets, and JSPs should be configured on the host server. The deployment descriptor also allows you to configure application specific HTTP properties, such as MIME types and per-file security constraints. To tie it all together, a Web application provides an abstract naming convention for the JNDI names of database connections and EJBs. See Chapter 22, "Creating Web Applications" in the Jaguar CTS Programmer's Guide for more information.

J2EE application support

A J2EE application is a unit of deployment for Web applications and Enterprise JavaBean components. The application contents can be archived in an Enterprise application Archive (.ear) file for easy installation and configuration on different servers. See Chapter 4, "Managing Applications and Packages in Jaguar Manager" in the Jaguar CTS Programmer's Guide for information on how to install and configure J2EE applications.

Support for standard Java back-end APIs

In accordance with the J2EE platform specification, Jaguar supports the following back-end APIs:

Enhanced JDBC and transaction support Jaguar 3.6 supports the standard JDBC connection caching model defined in the JDBC 2.0 specification. If you have a JDBC 2.0 driver, you can use this model rather than Jaguar's Java Connection Manager (JCM) API. Jaguar also implements the transaction support required by the J2EE and EJB 1.1 specifications. For more information about transactions, see Chapter 3, "Understanding Transactions and Component Lifecycles" in the Jaguar CTS Programmer's Guide. For information on configuring a JDBC driver, see Chapter 1, "Jaguar Configuration" in the Jaguar CTS System Administration Guide.
Enhanced Java Naming and Directory Support (JNDI) Java servlets, JSPs, and EJB components can now use aliased JNDI names to refer to EJB home interfaces, database connections, and JavaMail servers. Using aliases in your Web and EJB components can simplify the reconfiguration that is necessary when the component is deployed on another server; rather than fixing broken dependencies in source code, you can fix them in the component's external configuration. For more information, see Chapter 2, "Jaguar Naming Services" in the Jaguar CTS System Administration Guide.
JavaMail API JavaMail is a standard Java API. In Jaguar 3.6, you can use JavaMail to send mail from a Java component, JSP, or servlet. For example, you may wish to send confirmation email from an online ordering application. For more information, see Chapter 30, "Creating JavaMail" in the Jaguar CTS Programmer's Guide .

Running the Java Pet Store sample application

Sun Microsystems has created a large, comprehensive sample application developed to run on J2EE compliant servers. The application simulates an online pet store implemented with Java Server Pages, Java servlets, and Enterprise Java Beans. You can download eStore as part of the Sun Microsystems J2EE Blueprints .

For information on running the Java Pet Store (eStore) sample in Jaguar CTS, see the Sybase EAServer Web site .