New features of the JBOSS EAP 6 Series

In the project, the architecture is SPRINGMVC+SPRING+EJB+JPA architecture, of course, the server is JBoss, this time jboss we are using the new features of JBOSSEAP6.2,JBOSS7 and JBOSS4, 5 of the big change is:

Module declaration type Container

JBOSS EAP no longer has the concept of lib, everything is module. Either the Lib of the system call, the user-compiled Lib, or the third-party lib that the application refers to is built in a modular way, and where it is used, it is declared which module is used. This brings two benefits,

1. According to the official statement provides a completely modular class loading system, JBoss will load or unload the class according to the specific needs, only to maintain the resources currently in use, while exposing only the actual use of the API, but also increase the security of the system. JBOSSEAP6 starts and restarts quite quickly compared to previous jboss, which can reduce the waiting time for our development environment.
2. The problem of previously prone package conflicts is avoided by specifying which modules the application relies on.

after looking at the configuration of the data source "Oracle Data Source configuration-Understanding the use of the module" article will have a simple understanding of the module. Then there is the article "EJB implementation-through modules", which provides an in-depth overview of the module in JBoss EAP 6.2.

JBoss's full support for JEE6

(with a sentence, it is because of the strong JEE6 to promote the official and civil technology competition in the highly integrated, everyone will not contend with spring or EJB, see Spring and the JSR is not difficult to find, they are already merging with each other)

several notable benefits of JEE6 to JBoss EAP include

1. On the basis of the above described modular class loading system avoids the packet conflict, JEE6 's strict configuration of EJB project also provides a good solution to the problem of packet conflict. The manifast must indicate the module on which it is dependent. EJB implementation-A module that runs through all the Times.

2. Jndi full upgrade, so that the name of the bean and the client stub location is well resolved: EJB Jndi names can no longer be arbitrarily customized, Ejbjndi's full name specification:

Java:global[/<app-name>]/<module-name>/<bean-name>[!<fully-quali?fied-interface-name>]

It contains the war package name App-name,jar package name Module-name, custom bean name Bean-name, the full address name of the interface, and stateful if you need to declare stateful. such as: commondao/utm/common_dao!com.hp.ngoss.utm.commondao.commondaobusiness

The client of EJB3.1 JBoss has two topics detailing the EJB3.1 JNDI that is loved and hated and the removal of jboss-ejb-client.properties.

3. For singleton Session Bean support, each virtual machine provides only one instance, and the singleton mode is implemented at the application level.

4. Provide asynchronous methods (asynchronous methods), EJB supports the future way to achieve interactive results, improve thread utilization. See this series of articles: "Asynchronous Bean"

5. The full support of JPA (HIBERNATE4) simplifies the development of the persistence layer. See this series of articles "Jpa/hibernate"

6. Session Bean without interface. Not recommended, reason: neither CORBA nor Web service have said no stub concept. Similarly, EJB to be able to be called, need to know the interface, does not provide the interface of the way necessarily need to create the interface at the time of invocation and corresponding input and output parameter information, so as to increase the traffic overhead of transmission, of course, it is not completely worthless, for service providers are third-party customers, sometimes do not provide programming interfaces, This can be used in this way, but usually the service confession is friendly with the client, providing the interface directly to the customer without violating the conscience. It is not recommended to use this method based on the previously mentioned problem.

7. Implement the session Bean in a dynamic Web project. Deprecated, this makes the web layer in Jee's 4-tier architecture confusing with the business layer, which is not recommended for decoupling purposes. Possible usage scenarios, JBoss's own EJB provided only to its own web tier, without distributed scenarios.

8. Managed domains: The management domain organizes the virtual service on each physical machine as a service group, so that all servers are uniformly configured and deployed uniformly in one place. Machines configured for the same service group can be automatically scaled, or multiple instances can be set on a single host based on different port bindings. Managed domain to differentiate and cluster,cluster the main function is load balancing, disaster tolerance, and Managed domain is mainly the purpose of unified management. This series eight "Managed Domains" details the implementation of a management domain, and explains the unified configuration of the management domain, the characteristics of unified deployment. This series of nine "Cluster load Balancing clusters" describes how JBoss EAP 6 (JBOSSAS7) is configured for clusters.

Finally, it is also the most complained about the open source products (Chaos + complex) Solution: EAP version has technical support, application server configuration and related technical issues are uncertain, you can find Redhat technical staff to help (external network support).

In addition to the above introduction, there are many other new features such as:

Manage containers in multiple ways: Web pages, CLI clients, and configuration files. For example, there will be two kinds of jbosseap data source configuration, one is the CLI side +web page configuration, a direct in the configuration file, in fact, the effect is the same, but the configuration file configuration will not leave any traces, inconvenient retrospective. However, personal feeling in the actual application, especially in automatic deployment, or in the form of configuration files to manage the container is more practical.

While looking at the benefits of JBoss EAP, it is also expected that JBoss EAP will provide more professional capabilities to facilitate development and implementation (such as auto-upgrade applications), just like application servers operated by vendors such as WebLogic. At the same time, the open source community will be able to maintain the diversity of inclusiveness and technology, more open to try new technologies, new architectures, new ideas.

Summary

New things are not scary, fear is the fear of the heart, new things, new structure, new ideas-standing on the shoulders of giants, grow fast!

New features of the JBOSS EAP 6 Series