]]>
榪囧幓鍦ㄧ敤 JBoss 4.0.5 鐨勬椂鍊欎竴鐩磋 Log 鐨勯棶棰樺洶鎵幫紝濡傛灉鍦ㄨ嚜宸辯殑欏圭洰閲屽姞鍏?log4j 鍜?common logging 鐨勮瘽錛屽繀鐒朵細鍑洪敊錛屾墍浠ユ垜浠笉寰椾互錛屽繀欏婚氳繃涓浜涜皟鏁存墜孌墊潵澶勭悊榪欐牱鐨勯棶棰橈紝涔熷氨鏄瘡嬈″湪 tomcat 涓嬭皟璇曠殑搴旂敤錛岄渶瑕佹敼鐐逛笢瑗挎墠鑳?deploy 鍒?JBoss 涓婂幓錛屼絾浣跨敤浜?4.2 浠ュ悗灝辨病鏈夎繖鏍風殑闂浜嗭紝鍦?tomcat 涓嬬敤鐨勫寘鐩存帴鏀捐繃鍘伙紝娌℃湁鍋氫換浣曠殑淇敼灝卞彲浠ユ甯鎬嬌鐢ㄤ簡銆?br>
鍥犱負鎴戦」鐩敤鐨勬槸 commons-lang 2.3 鑰?JBoss 4.0.5 鐢ㄧ殑鏄?2.1 姣忔浣跨敤 commons-lang 2.1 閲岄潰娌℃湁鐨勬柟娉曟椂錛屽氨浼氬嚭鐜?NoSuchMethodException錛屾渶鍚庡彧濂芥妸 JBoss 涓嬫墍鏈夌殑 commons-lang 鐨勫寘鐢?2.3 鐨勬浛鎹㈡帀錛岃?4.2 宸茬粡娌℃湁榪欎釜闂浜嗭紝2.3 宸茬粡鍙互姝ｅ父浣跨敤浜嗐?br>
榛樿鐨?JBoss 4.2 鎴戝彧鑳界敤 localhost 璁塊棶錛屼笉鑳界敤 IP 鍦板潃璁塊棶錛屽悗鏉ュ彂鐜幫紝闇瑕佷慨鏀?jboss-4.2.0.GA\server\default\deploy\jboss-web.deployer\server.xml 鎶?Connector 涓嬮潰鐨?address 鏀規垚瀵瑰簲鐨?IP 鎴栬?0.0.0.0 灝卞彲浠ョ敤 IP 璁塊棶浜嗐?nbsp;
鍚庨潰闄勪笂浜?Release Note 涓殑涓浜涘唴瀹廣?br>
This is the final release of JBoss Application Server v4.2.0. JBoss AS 4.2 is a stepping stone from JBoss 4.0 to JBoss 5.0. It combines a lot (but not all) of the exciting new features of JBoss 5, but based on the stable 4.x MicroKernel architecture.
Highlights
* JDK5 is *required* to run JBossAS 4.2.x. The decision was based on the fact that JDK1.4 is phased out and the reality that a lot of people like Java Annotations support and want to combine EJB3 and JBoss Seam components with JBossAS. JDK6 is not formally supported yet, although you may be able to start the server with it. JDK6 support will come with JBossAS 5.x.
* JBoss EJB3 is now deployed *by default* in JBossAS 4.2.x The fact that we base on JDK5 makes our life easier in this regard, meaning we don't have to maintain jdk5 code retro-weaved for jdk1.4 runtimes, and we can include by default components that require jdk5 to run.
* JBoss Web v2.x is the web container in JBossAS 4.2, an implementation based on Apache Tomcat that includes the Apache Portable Runtime (APR) and Tomcat native technologies to achieve scalability and performance characteristics that match and exceed the Apache Http server. In the absence of the native libraries in the JBoss classpath, JBoss Web falls back to the standard non-native connector mode. The native libraries need to be downloaded and installed separately.
* JBoss Transactions v4.2 is the default transaction manager for JBossAS 4.2. JBoss Transactions is founded on industry proven technology and 18 year history as a leader in distributed transactions, and is one of the most interoperable implementations available. The JTA version of JBoss Transactions included with the server provides for fully recoverable transactions. For distributed transaction support the JTS version of JBoss Transactions will need to be used. Furthermore, it is always possible to fall back to the legacy JBossTM fast in-memory transaction manager implementation, if necessary.
* JBossWS is the web services stack for JBoss 4.2 providing Java EE compatible web services. It has been upgraded to v1.2.1.GA
* JGroups/JBossCache were upgraded to the latest releases. The server is already configured to support channel multiplexing, when it becomes available.
* JBoss Remoting was upgraded to the latest stable 2.2.x version. This was done in order to align dependencies with the thirdparty libraries required by the new JBoss Messaging, which means that, if you want, you can replace the default JBossMQ messaging provider with JBoss Messaging, without having to revert to a scoped deployment.
]]>