[jboss-cvs] JBossAS SVN: r61133 - branches/Branch_4_2/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Mar 6 03:28:44 EST 2007
Author: dimitris at jboss.org
Date: 2007-03-06 03:28:44 -0500 (Tue, 06 Mar 2007)
New Revision: 61133
Modified:
branches/Branch_4_2/build/docs/readme.html
Log:
give more emphasis to the security warning.
Modified: branches/Branch_4_2/build/docs/readme.html
===================================================================
--- branches/Branch_4_2/build/docs/readme.html 2007-03-06 07:46:49 UTC (rev 61132)
+++ branches/Branch_4_2/build/docs/readme.html 2007-03-06 08:28:44 UTC (rev 61133)
@@ -108,19 +108,19 @@
<p>Plus more than 50 bug fixes, see the <a href="#Details">Detailed Release Notes</a>
section for the full details.</p>
<h2><a name="Compatibility">Compatibility Issues</a></h2>
-This lists the changes that could affect compatibility.<ul>
+This lists the changes that could affect compatibility.
+<ul>
<li>A JavaSE 5 runtime is required to run JBossAS 4.2. A full JDK with
tools.jar support is no longer needed by jboss, since JBoss Web packages the
eclipse JDT compiler for compiling JSP pages and javassist has its own
internal compiler. JAVA_HOME can point to a JRE,
<a href="http://jira.jboss.com/jira/browse/JBAS-4161">JBAS-4161</a>.</li>
- <li>
- <p>According to our
+ <li>According to our
<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning">product versioning rules</a>,
JBossAS 4.2 is a minor upgrade against JBoss AS 4.0. The various JBoss APIs
should be stable but backwards compatibility for individual component
implementations may not be guaranteed, e.g. interoperating with another
- JBoss instance that uses an older version of JGroups.</p></li>
+ JBoss instance that uses an older version of JGroups.</li>
<li>Tomcat 6 is now bundled as part of JBoss Web.
deploy/jbossweb-tomcat55.sar has been replaced by deploy/jboss-web.deployer.</li>
<li>conf/log4j.xml has been renamed to conf/jboss-log4j.xml, to allow
@@ -144,8 +144,11 @@
instead of binding to all available interfaces (0.0.0.0). This was primarily
done for security reasons because of concerns of users going to production
without having s<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss">ecured
- their servers properly</a>. To bind JBoss services to a particular
- interface, simply run jboss with the -b option.</li>
+ their servers properly</a>. To enable remote access by binding JBoss
+ services to a particular interface, simply run jboss with the -b option, but
+ be aware you still need to
+ <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss">secure you
+ server properly</a>.</li>
<li>There now distinct properties to configure the various mcast ports,
<a href="http://jira.jboss.com/jira/browse/JBAS-4021">JBAS-4021</a>.</li>
<li>JBoss EJB3 is now included by default. If you don't need/want EJB3
More information about the jboss-cvs-commits
mailing list