Step into Java (ii) The specification explanation of EE

I. BACKGROUND

at first, each company developed its own components, but in the process of user use, the components of each family are not universal, incompatible. So the Java protocol is proposed, which is a series of standards based on the technology.

Java The platform consists of a set of services ( Services ), application interfaces ( APIs ) and protocols, which are fully functional for data processing and server-side applications. It provides functional support for developing multi-tier Web-based applications. Applications deployed using the EE technology are: "Write once, run anywhere".

the components of the client (tier) include applets , Application , Html three kinds.

Application server, is packaged components, protocols, services;

EIS , typically a database system, but also includes directory services, ERP (Enterprise resource planning). Focus on understanding The specification of:

Second, the standard specification of components

1 , JDBC ( javadatabase Connectivity )

similar to Microsoft's ODBC , both of which are open connection databases.

2 , JNDI ( Java nameand Directory Interface)

Java naming and directory interfaces, providing a consistent model to access files, objects, because the system scale, the use of distributed, the need to unify the files on multiple servers, unified naming and directory interface, more convenient management.

3 , EJB ( Enterprisejavabean )

provides a framework specification for a distributed service. The System file program is distributed on multiple servers, and a business logic may invoke EJB components distributed across multiple servers to achieve distributed and reduce the pressure of big data access.

Bean is intended to refer to a pod (shell),JavaBean like an empty container, no data, and so on when the runtime fills the data. It is once written, executed anywhere.

4 , RMI ( Remote Methodinvoke )

Remote Method invocation. It is a lower-level protocol used by the EJB to pass data between the client and the server using serialization .

5 , CORBA

used to assemble new applications and legacy systems together. Specific application, to be practiced.

6 , JSP

composed of HTML code and embedded java code, the browser makes a page request and then processes the Java Code , and then return the generated HTML page to the browser.

7 , Java Servlet

A servlet is a small Java program that provides much more functionality than JSPs, but is implemented in a different way. JSPs are usually embedded in a small amount of Java code in most HTML code, and the servlet is all written in Java and generates HTML.

8 , XML

Extended Markup Language, which is used to set languages for other markup languages. XML is platform independent, and the development of Java is independent of each other. It is because of the platform independence of XML that the Java cross-platform has a strong backing.

9 , JMS ( Java Messageservice )

A Communication application interface that provides messaging, transactional message delivery, consistent messaging, and the ability to integrate with new and legacy backend systems.

Ten , JTA ( javatransaction API )

Defines a standard APIthat allows applications to access various transaction monitoring.

One , JTS

is The basic implementation of CORBA transaction monitoring.

A , JavaMail

an API for accessing mail servers that supports SMTPandIMAP servers.

- , JAF (JavaBeans Activation Framework)

These norms, initial contact to understand their respective areas of demarcation, the standard of business, until the practice process, and then one by one corresponds to the theory we have learned now. The general sense of the advent of the Java standard, is to unify common, to deal with complex business, big data, high concurrency, distributed.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Step into Java (ii) The specification explanation of EE