Java Technology Standard Components introduction Daquan

· Enterprise JavaBeans (EJB) technology uses a component model to simplify the development of middleware applications, providing automatic support for services such as transaction, security, and database connectivity. (See tutorial "Enterprise JavaBean Basics"; see EJB Best Practices Series; read "Designing Enterprise applications using EJB 3.0 Java Persistence APIs". ）

· The Portlet specification defines a set of APIs for Java Portal computing that can address aggregation, customization, presentation, and security issues. (see "Using Apache Pluto to build and test JSR 168 compliant portlets".) ）

· JavaMail is an API that provides a set of abstract classes for modeling messaging systems. (See tutorial "JavaMail API Basics Tutorial.") ）

· Java message Service (JMS) is an API that defines a common set of message concepts and programming policies for all messaging systems that are compatible with JMS technology, thereby supporting the development of portable, text-based Java applications. (See Tutorial "Introduction to Java Messaging Services.") ）

· JavaServer Faces (JSF) provides a programming model that helps developers assemble reusable UI components into a page, connect these components to an application data source, connect client-generated events to server-side event handlers, and easily build Web applications. (See the JSF columns and tutorials for skeptics, "UI development with JavaServer Faces", and JavaServer Faces technical topics.) ）

· JavaServer pages (JSP) allows web developers to quickly develop and easily maintain dynamic, platform-independent web pages, isolating user interfaces and content generation, so that designers can modify page layouts without having to modify dynamic content. This technique uses XML-like markup to encapsulate the logic for page-generated content. (See Tutorial "Getting Started with JSP technology" and refer to the JSP Best practice series, as well as JavaServer Pages technical topics.) ）

· Standard tag Library for JavaServer Pages (JSTL) is a collection of custom tags that enable many common Web site features in a standardized format. (see "Using JSTL to update JSP pages" and a four-part article series "Getting Started with JSTL.") ）

· Java Servlets provides a component-based, platform-independent approach to building web-based applications while avoiding the performance constraints of CGI programs, extending and enhancing the functionality of Web servers. (Tutorial "Introduction to Java Servlet Technology" helps you understand Java Servlets.) ）

· Java EE Connector Architecture (JCA) defines a standard architecture for Enterprise information Systems (EIS) that connects the Java platform to various structures, defining a scalable and secure transactional mechanism To enable EIS vendors to provide standard resource adapters that can be inserted into the application server. (see "Understanding JCA Transaction", "Select JCA for EAI, JMS or Web service", "Integrate remote Enterprise information systems with JCA, JMS, and Web Servic Es "and tutorial" Introduction to the "Connector architecture". ）

· Java EE Management Specification (JMX) defines an information management model for the Java EE platform. According to its design, the Java EE Management model can interoperate with a variety of management systems and protocols; a standard mapping of the model to the Common Information Model (CIM), which is an SNMP Management Information Base (MIB), which can also be mapped to the Java object model through an EJB component that resides on the server--j2ee Management EJB Component (MEJB). (see "From the black box to the Enterprise, part 1th: Management, JMX 1.1 style".) ）

· The Java Transaction API (JTA) is an advanced API independent of implementation and protocol that enables applications and application servers to access transactions. The Java Transaction Service (JTS) specifies the implementation of the Transaction Manager, which supports JTA and implements the OMG Object Transaction Service (OTS) 1.1 on the layer below this API The Java mapping for the specification. JTS uses the Internet inter-orb Protocol (IIOP) to propagate transactions. (See "Understanding JTS--The introduction to transactions". ）