The following features were introduced in version 3.6.
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/
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:
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:
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:
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.
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.
In accordance with the J2EE platform specification, Jaguar supports the following back-end APIs:
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 .
PowerJ 3.6 supports the Java 2 platform, Enterprise Edition (J2EE) application standard for developing applications for the Web. This new release of PowerJ allows you to develop and deploy J2EE applications containing Enterprise JavaBeans (EJB), Java servlets, and JavaServer Pages (JSP). See Chapter 7, "Developing Applications with PowerJ and EAServer" for more information.
ActiveX now supports additional datatypes and provides a model for the handling of non-fatal errors inline. See these chapters in the Jaguar CTS Programmer's Guide for more information:
Jaguar 3.6 includes a message service that can be used for asynchronous event notification. The message service is implemented as a Jaguar component with interfaces specified in standard CORBA IDL. Consequently, it can be used by all types of clients and components. See Chapter 31, "Using the Message Service" in the Jaguar CTS Programmer's Guide for more information.
Jaguar 3.6 includes a Thread Manager component that can be used to spawn, suspend, and stop threads that execute a component instance. Using threads, you can implement server-side processing that must execute independently of client requests. The Thread Manager augments the existing support for Jaguar service components. See Chapter 32, "Using the Thread Manager" in the Jaguar CTS Programmer's Guide for more information.
Using Sybase Adaptive Server Enterprise 12.0 with the high-availability option, you can configure highly available databases for use by Jaguar components. See Chapter 4, "Load Balancing, Failover, and Component Availability" in the Jaguar CTS System Administration Guide for more information.
| Copyright © 2000 Sybase, Inc. All rights reserved. | ||