JBoss4.0 overview
Open source application server simplifies complex operation, new feature translator of AOP: I am not very familiar with JBoss4.0, so some new concepts and knowledge understanding is also inevitable, especially AOP knowledge. During the translation of this article, some concepts and semantics are really not very accurate. I hope that there are experienced and understanding friends in this regard, welcome to more opinions. The preambularly JBoss 4.0 is an application server installation, including the EJB2.0 container, Java message service, and the like, but his face-oriented design (AOP) is part of its truly prominent. JBoss4.0 has a lot of advantages. It is not only an open source, platform independent, comprehensive J2EE supports application servers and installation is also very simple. JBoss includes a web server (servlet / JSP container, HTML server), EJB2.0 container. Complete pure Java database engine, (Java message service) JMS, JavaMail, and Java transaction API / Java Transaction Service (JTA / JTS) support. Early JBOSS used the Apache Tomcat web server, but Apache Tomcat was already in JBoss in JBoss4.0. JBoss4.0 is released at this year's Javaone conference. The JBoss organization puts this version of JBoss as a development version to test the test. Official product levels are expected to be released from the fourth quarter of this year. The new features include, integrated Java data object (JDO), fixes for JMS multi-point transfer mechanisms, full implementation and distributed transaction mechanisms for J2EE 1.4. Install JBoss4.0 is very simple: First understanding the JBoss package file is configuring some environment variables. Suppose I have a WAR file now and this file has been tested using JDBC. When JBoss is running normally, I put this WAR file in the JBoss deployment directory, and the thermal deployment of JBoss can automatically deploy this WAR. It is about 10 minutes from download JBoss to install and run my app. JBoss's application server controls and configures the -JMX mechanism, running all components and services at a time. Resource properties and configurable parameters can be mappled and changed by MBeans (controllable beans), which can be set in JBoss console. Once our servlet-based application is deployed, JBoss automatically installs a deployment MBeans, which will be added to the navigation menu of the JMX console. You can deploy or uninstall or uninstall the WAR application or view the application-related properties. It is undeniable that JBoss's console is more simple than IBM's WebSphere or Bea's WebLogic, but the effect is the same. In addition, since JBoss is a development source code, you can share the console as you want. Aspects introduces the new features of JBoss4.0 reflected in aspect design (AOP). By appropriate expansion, AOP allows you to describe a class similar to shared from the parent class. In JBOSS, AOP features have many benefits. The most important feature is that it can "inject" a behavior in your class without changing the source code. This feature allows you to maintain the persistent line of the object, enable the object's method "purposeful processing" ("Transaction Aware,") and enables a class to integrate. JBoss AOP architecture is responsible for processing AOP, using a set of naming concepts, such as "Interceptor," Pointcut, ", and" Introduction ". An Interceptors encodes "Intercepts", which puts an object in an intercepted class.
