[jboss-cvs] JBossAS SVN: r95590 - projects/docs/enterprise/5.0/Getting_Started_Guide/en-US.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Oct 26 23:37:23 EDT 2009


Author: laubai
Date: 2009-10-26 23:37:23 -0400 (Mon, 26 Oct 2009)
New Revision: 95590

Modified:
   projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
   projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
Log:
Added changes for JBPAPP-2960.

Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml	2009-10-27 03:29:39 UTC (rev 95589)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml	2009-10-27 03:37:23 UTC (rev 95590)
@@ -13,11 +13,11 @@
 	
 	<section>
 		<title>
-			Unimplemented features
+			Further Release Information
 		</title>
 		
 		<para>
-			The Release Notes for JBoss Enterprise Application Platform contain information on EJB3 features that are not yet implemented, or partially implemented. The Release Notes include links to issues in JIRA for information on workarounds and further details.
+      The Release Notes for JBoss Enterprise Application Platform may contain updated information on new and modified features. The Release Notes also include links to issues in JIRA for issue details and information about workarounds.
 		</para>
 	</section>
 			

Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml	2009-10-27 03:29:39 UTC (rev 95589)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml	2009-10-27 03:37:23 UTC (rev 95590)
@@ -8,7 +8,7 @@
 			Move to <filename class="directory">JBOSS_DIST/jboss-as/bin</filename> directory and execute the <literal>run.bat</literal> (for Windows) or <literal>run.sh</literal> (for Linux) script, as appropriate for your operating system. 
 		</para>
 		<para>
-			There is no <literal>Server Started</literal> message shown at the console when the server is started using the <literal>production</literal> profile, which is the default profile used when no other is specified. This message can be found in the <filename>server.log</filename> file located in the <filename>JBOSS_DIST/jboss-as/server/production/log</filename> subdirectory.
+			There is no <literal>Server Started</literal> message shown at the console when the server is started using the <literal>production</literal> profile. This message can be found in the <filename>server.log</filename> file located in the <filename>JBOSS_DIST/jboss-as/server/production/log</filename> subdirectory.
 		</para>
 <important><title>Remote connection to the JBoss Enterprise Application Platform server</title>
 	<para>the JBoss JBoss Enterprise Application Platform now binds its services to localhost (127.0.0.1) by default, 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 secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux and <command>run.bat -b 0.0.0.0</command>. In any case, be aware you still need to secure your server properly.




More information about the jboss-cvs-commits mailing list