[Some architectures in Java web]2\web development

1, Enterprise development structure:

Enterprise platform development of a large number of B/s development model, no matter what dynamic Web implementation means, its operation is the same, most of its core operations are around the database. However, if you use the programming language for database development, to involve a lot of things such as transaction, security and other operational issues, so now development is often through the middleware to transition, that is, the program runs on the middleware, and through the middleware operating system operations, and specific related processing, such as transaction, security, etc. completely by the middleware to take responsibility , so that programmers can only complete the specific function development.

2. Java EE Architecture:

Java EE is built on the basis of Java SE. NET also comes from Java EE.

2.1. Four containers:

Applet Container, Application Container, Web Container, EJB Container are responsible for each other, do not affect, if you want to run a Web program, you must be a Web container.
2.2. Java EE components:

Applets, application, Jsp/servlet, EJBS each run their own components, each of which implies a program development.

2.3. Java EE Service:

HTTP (Hypertext Transfer Protocol): Primary communication protocol

RMI-IIOP (invocation over the Internet inter-orb Protocol): Remote method invocation

Java IDL (Java Interface definition Language): Java Interface Definition language, primarily for accessing external CORBA services

JTA (Java Transaction API): API for transactional processing, but all transactions in Java EE should be handed to the container for processing

JDBC (Java database Connectivity): Provides a set of APIs for database operations

JMS (Java message Service): For sending point-to-point messaging services, additional messaging middleware support is required
JavaMail: For sending mail, additional mail service support is required

JAF (JavaBeans Activation Framework): Message data for encapsulating delivery

JNDI (Java naming and Directory Interface): "Key-value" provides a name binding and relies on the name of the binding to obtain a specific object

JAXP (Java API for XML parsing): APIs specifically for XML parsing
JCA (ee Connector Architecture): Java connector Architecture, which enables you to connect applications with different development architectures
JAAS (Java authentication and Authorization Service): Used to authenticate user actions to make the current running code more reliable

JSF (Java Server Faces): official MVC Implementation Component

JSTL (JSP standard Tag Library): JSP page Tag Support Library

SAAJ (SOAP with Attachments APIs for Java), JAXR (Java APIs for XML registries): Web Services components, primarily for heterogeneous distributed service development

3. The location of Java EE in the Enterprise Application environment:

Just a component of the middle tier!

4. Java EE core Design pattern: MVC (Mode-view-controller)

5. Struts Development Framework:

With the use of standard MVC design patterns for development, there are certainly too many complex designs, and struts is a set of frameworks for MVC development. Obviously, struts here is a combination of JSP and servlet, or a disguised application.