. Net personnel use Java EE

Part 1ArticleThe basic concepts of Java are briefly summarized (http://www.cnblogs.com/2018/archive/2011/04/05/1993163.html), this paper summarizes the learning process of Java ee.

Basic

Https://javaeetutorial.dev.java.net/files/documents/7232/141115/javaeetutorial6.zip

This contains the introduction documents and examples.CodeThese examples can be opened directly in netbeans. refer to the document for deployment and operation.

This document introduces the basic concepts and examples of the entire Java EE, and is familiar with this basic concept of Java ee.

Basic concepts of Java EE

In actual development, as long as you understand the following charts and specifications, you only need to learn specific specifications and standards. Because Java ee has a wide range of specifications, we actually use only some of them.

[The following are some books and materials records, which I think are very important]

Java EE is based on standards.

Containers are Java EE runtime environments that provide certain services to the components they host such as life-cycle management, dependency injection, and so on. these components use well-defined contracts to communicate with the Java EE infrastructure and with the other components.

 

Containers

Applet containersAre provided by most Web browsers to execute applet components. when you develop applets, you can concentrate on the visual aspect of the application while the container givesou a secure environment. the applet container uses a sandbox security model where code executed inhe "sandbox" is not allowed to "play outside the sandbox. "this means that the container prevents anyode downloaded to your local computer from accessing local system resources, such as processes oriles.

The application client container (ACC)Except des a set of Java classes, libraries, and other files required to bring injection, security management, and Naming Service to Java SE applications (swing, atch processing, or just a class with a main () method ). ACC communicates with the EJB container usingrmi-IIOP and the Web Container with HTTP (e.g ., for Web Services ).

The Web ContainerProvides the underlying services for management and executing Web componentsservlets, ejbs lite, JSPs, filters, listeners, JSF pages, and Web Services ). it is responsible for instantiating, nitializing, and invoking servlets and supporting the HTTP and HTTPS protocols. it is the containersed to feed web pages to Client browsers.

The EJB containerIs responsible for managing the execution of the enterprise beans containing theusiness logic tier of your Java EE application. it creates new instances of ejbs, manages their life cycle, and provides services such as transaction, security, concurrency, distribution, naming service, or theossibility to be invoked asynchronously.

Services

Containers provide underlying services to their deployed components.

•Java transaction API (JTA ):This service offers a transaction demarcation API usedby the container and the application. It also provides an interface between thetransaction manager and a resource manager at the service provider interface (SPI) level.

•Java persistence API (JPA): STandard api for object-relational mapping (ORM). With its Java persistence Query Language (jpql), you can query objects stored in the underlying database.

•Validation:Bean validation provides a class level constraint declaration and validation facility.

•Java Message Service (JMS ):This allows components to communicate asynchronously through messages. It supports reliable point-to-point (P2P) messaging as well as the publish-subscribe (pub-sub) model.

•Java Naming and Directory Interface (JNDI ):This API, encoded in Java SE, is used to access naming and directory systems. your application uses it to associate (BIND) names to objects and then to find these objects (lookup) in a directory. you can look up CES, JMS factories, ejbs, and other resources. omnipresent in your code until J2EE 1.4, JNDI is used in a more transparent way through injection.

•Javamail:Applications require the ability to send e-mails, which can be implemented through use of the javamail API.

•JavaBeans activation framework (JAF ):The jaf api, included in Java SE, provides a framework for handling data in different MIME types. It is used by javamail.

•XML processing:Most Java EE components can be deployed with optional XML deployment descriptors, and applications often have to manipulate XML documents. the Java API for XML Processing (JAXP) provides support for parsing documents with Sax and Dom APIs, as well as for XSLT. the streaming API for XML (Stax) provides a pull-parsing API for XML.

• Java EE Connector Architecture (JCA ):Connectors allow you to access EIS from a Java EE component. These cocould be databases, mainframes, or enterprise resource planning (ERP) programs.

• Security Services:Java authentication and authorization Service (JAAS) enables services to authenticate and enforce access controls upon users. the Java Authorization Service Provider contract for containers (jacc) defines a contract between a Java EE application server and an authorization service provider, allowing custom authorization service providers to be plugged into any Java EE product.

• Web Services:Java EE provides support for soap and restful Web Services. the Java API for XML Web Services (JAX-WS), replacing the Java API for XML-based RPC (JAX-RPC), provides support for web services using the SOAP/HTTP protocol. the Java API for restful Web Services (JAX-RS) provides support for web services using the REST style.

• Dependency injection:Since Java ee 5, some resources (datasources, JMS factories, persistence units, ejbs ...) Can be injected in managed components. Java EE 6 goes further by using CDI (context and dependency injection) as well as the di (dependency injection for Java) specifications.

• Management:Java EE defines APIs for managing containers and servers using a special management enterprise Bean. the Java Management Extensions (JMX) API is also used to provide some management support.

• Deployment:The Java EE deployment Specification defines a contract between deployment tools and Java EE products to standardize application deployment.

References

Java EE 6 standard Chinese version. CHM

Java + EE + 6 + API + specifications. CHM

Javadocee6.zip

Servlet-2_3-fcs-docs.zip

Javaeetutorial6.zip [the Java EE 6 tutorial]

The Java EE 6 tutorial basic concepts, 4th edition

Beginning Java EE 6 with glassfish 3, 2nd Edition

These materials can be found online.

Examples

Http://netbeans.org/kb/docs/javaee/ecommerce/design.html

A very practical example covers multiple aspects. It is clear to understand how to implement a Java EE Project.

Java ee has been developing for more than a decade, and relevant materials and open-source frameworks are vast. We only need to grasp these basic concepts, and then learn from the corresponding examples and perform development and transformation, it can be applied smoothly in the project.