[jboss-cvs] JBossAS SVN: r92298 - projects/docs/enterprise/5.0/Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 13 01:54:10 EDT 2009
Author: irooskov at redhat.com
Date: 2009-08-13 01:54:10 -0400 (Thu, 13 Aug 2009)
New Revision: 92298
Modified:
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/About_the_Example_Applications.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Book_Info.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Seam.xml
Log:
corrected sections in getting started guide as per JBPAPP-2432
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/About_the_Example_Applications.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/About_the_Example_Applications.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/About_the_Example_Applications.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -5,7 +5,7 @@
<chapter id="About_the_Example_Applications">
<title>Sample Applications</title>
<para>
- The JBoss Application Server, ships with various sample applications under <literal>JBOSS_HOME/docs/examples</literal>.
+ The JBoss Enterprise Application Platform, ships with various sample applications under <literal>JBOSS_HOME/docs/examples</literal>.
</para>
<para>
For further details, please refer to the accompanying <filename>readme.txt</filename> for the respective sample applications under the above directory.
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Book_Info.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Book_Info.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -9,7 +9,7 @@
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>5.0</productnumber>
- <pubdate>, 2009</pubdate>
+ <!--<pubdate>, 2009</pubdate> -->
<isbn>N/A</isbn>
<abstract><para>This Getting Started Guide documents relevant information regarding
the initial use of the JBoss Enterprise Application Platform</para>
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-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -4,11 +4,11 @@
<chapter id="EJB3_Caveats">
<title>
- EJB3 Caveats in JBoss Application Server 5.0.0
+ EJB3 Caveats in JBoss Enterprise Application Platform 5.0
</title>
<para>
- There are a number of implementation features that you should be aware of when developing applications for JBoss Application Server 5.0.0.
+ There are a number of implementation features that you should be aware of when developing applications for JBoss Enterprise Application Platform 5.0.
</para>
<section>
@@ -17,7 +17,7 @@
</title>
<para>
- The Release Notes for JBoss Application Server 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 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.
</para>
</section>
@@ -28,11 +28,11 @@
</title>
<para>
- JBoss Application Server 5 fully supports the entire Java 5 Enterprise Edition specification. JBoss Application Server 4.2.2 implemented EJB3 functionality by way of an EJB MBean container running as a plugin in the JBoss Application Server. This had certain implications for application development.
+ JBoss Enterprise Application Platform 5 fully supports the entire Java 5 Enterprise Edition specification. JEnterprise Application Platform 4.3 implemented EJB3 functionality by way of an EJB MBean container running as a plugin in the JBoss Enterprise Application Platform. This had certain implications for application development.
</para>
<para>
- The EJB3 plugin injects references to an EntityManager and @EJB references from one EJB object to another. However this support is limited to the EJB3 MBean and the JAR files it manages. Any JAR files which are loaded from a WAR (such as Servlets, JSF backing beans, and so forth) do not undergo this processing. The Java 5 Enterprise Edition standard specifies that a Servlet can reference a Session Bean through an @EJB annotated reference, this was not implemented in JBoss Application Server 4.2.2.
+ The EJB3 plugin injects references to an EntityManager and @EJB references from one EJB object to another. However this support is limited to the EJB3 MBean and the JAR files it manages. Any JAR files which are loaded from a WAR (such as Servlets, JSF backing beans, and so forth) do not undergo this processing. The Java 5 Enterprise Edition standard specifies that a Servlet can reference a Session Bean through an @EJB annotated reference, this was not implemented in Enterprise Application Platform 4.3.
</para>
<!--
<para>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -4,29 +4,29 @@
<preface id="Book-Preface">
<title>Introduction</title>
<para>
- JBoss Application Server is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. It's easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
+ JBoss Enterprise Application Platform is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. It's easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
</para>
<para>
- Because it is Java-based, JBoss Application Server is cross-platform, easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
+ Because it is Java-based, JBoss Enterprise Application Platform is cross-platform, easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
</para>
- <para>
- Installing JBoss Application Server is simple and easy. You can have it installed and running in no time. This guide will teach you to install and get started with the JBoss Application Server.</para>
+<!-- <para>
+ Installing JBoss Enterprise Application Platform is simple and easy. You can have it installed and running in no time. This guide will teach you to install and get started with the JBoss Application Server.</para> -->
<section id="Book-We_Need_Feedback">
<title>Help Contribute</title>
<para>
- If you find a typographical error in the <citetitle>Installation Guide and Getting Started Guide</citetitle>, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the project <citetitle>JBoss Application Server</citetitle> and component <citetitle>Docs/Installation and Getting Started Guide</citetitle>.
+ If you find a typographical error in the <citetitle>Installation Guide and Getting Started Guide</citetitle>, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the project <citetitle>JBoss Enterprise Application Platform</citetitle> and component <citetitle>Documentation</citetitle>.
</para>
<para>
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
</para>
- <note><title>Note</title><para>Be sure to give us your name so you can receive full credit.</para></note>
+ <!-- <note><title>Note</title><para>Be sure to give us your name so you can receive full credit.</para></note>
- <note><title>Note</title><para>This content is taken from svn.jboss.org/repos/jbossas/projects/docs/community/5 and has yet to be branched.</para></note>
+ <note><title>Note</title><para>This content is taken from svn.jboss.org/repos/jbossas/projects/docs/community/5 and has yet to be branched.</para></note>
<para>To access the content directly and make changes yourself:</para>
<screen>
- svn co https://svn.jboss.org/repos/jbossas/projects/docs/community/5 --username yourusername
- </screen>
+ svn co https://svn.jboss.org/repos/jbossas/projects/docs/community/5 username yourusername
+ </screen> -->
</section></preface>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -14,16 +14,16 @@
You don’t need a detailed understanding of the microcontainer to use JBoss, but it’s worth keeping a picture of this basic architecture in mind as it is central to the way JBoss works.
</para>
<para>
- The JBoss Application Server ships with three different server configurations. Within the <literal><JBoss_Home>/server</literal> directory, you will find five subdirectories:
- <literal>minimal</literal>, <literal>default</literal>, <literal>standard</literal>, <literal>all</literal> and <literal>web</literal> - one for each server configuration. Each of these configurations provide a different set of services. The <literal>default</literal> configuration is the one used if you don’t specify another one when starting up the server.
+ The JBoss Enterprise Application Platform ships with six different server profiles. Within the <literal><JBoss_Home>/server</literal> directory, you will find six subdirectories:
+ <literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literla>production</literal>, <literal>standard</literal> and <literal>web</literal> - one for each server profile. Each of these profiles provide a different set of services. The <literal>default</literal> configuration is the one used if you don’t specify another one when starting up the server.
</para>
<para>
<variablelist>
<varlistentry>
- <term>minimal</term>
+ <term>all</term>
<listitem>
<para>
- has a minimal configuration—the bare minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. This is what you would use if you want to use JMX/JBoss to start your own services without any other Java EE 5 technologies. This is just the bare server. There is no web container, no EJB or JMS support.
+ The all configuration starts all the available services. This includes the RMI/IIOP and clustering services, which are not loaded in the default configuration.
</para>
</listitem>
</varlistentry>
@@ -36,14 +36,22 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>all</term>
+ <term>production</term>
<listitem>
<para>
- The all configuration starts all the available services. This includes the RMI/IIOP and clustering services, which are not loaded in the default configuration.
+ is based on the "all" profile, tuned for production; with log verbosity reduced, deployment scanning every 60 seconds, and memory usage tuned to accomodate production deployment requirements, among other things. This is the configuration that will be used by the server when it is started, if no other configuration is specified.
</para>
</listitem>
</varlistentry>
<varlistentry>
+ <term>minimal</term>
+ <listitem>
+ <para>
+ has a minimal configuration—the bare minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. This is what you would use if you want to use JMX/JBoss to start your own services without any other Java EE 5 technologies. This is just the bare server. There is no web container, no EJB or JMS support.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
<term>standard</term>
<listitem>
<para>
@@ -751,19 +759,19 @@
</entry>
</row>
<row>
- <entry>hsqldb-ds.xml</entry>
+ <entry><literal>hsqldb-ds.xml</literal></entry>
<entry>configures the Hypersonic embedded database
service configuration file. It sets up the embedded
database and related connection factories. </entry>
</row>
<row>
- <entry>http-invoker.sar</entry>
+ <entry><literal>http-invoker.sar</literal></entry>
<entry>contains the detached invoker that supports RMI
over HTTP. It also contains the proxy bindings for
accessing JNDI over HTTP. </entry>
</row>
<row>
- <entry>jboss-local-jdbc.rar</entry>
+ <entry><literal>jboss-local-jdbc.rar</literal></entry>
<entry>is a JCA resource adaptor that implements the JCA
<literal>ManagedConnectionFactory</literal>
interface for JDBC drivers that support the
@@ -771,7 +779,7 @@
JCA. </entry>
</row>
<row>
- <entry>jboss-xa-jdbc.rar</entry>
+ <entry><literal>jboss-xa-jdbc.rar</literal></entry>
<entry>JCA resource adaptors for XA DataSources</entry>
</row>
<row>
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-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -12,7 +12,7 @@
</para>
</important>
<para>
- For more information including setting up multiple JBoss server instances on one machine and hosting multiple domains with JBoss, please refer to the <ulink url="http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta500/html-single/index.html">Administration and Configuration Guide</ulink>. Some examples on binding are shipped in <filename><JBOSS_HOME>/docs/examples/binding-manager/sample-bindings.xml</filename>.
+ For more information including setting up multiple JBoss server instances on one machine and hosting multiple domains with JBoss, please refer to the <ulink url="http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta500/html-single/index.html">Administration and Configuration Guide</ulink>. <!--Some examples on binding are shipped in <filename><JBOSS_HOME>/docs/examples/binding-manager/sample-bindings.xml</filename>-->.
</para>
<para>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -53,14 +53,14 @@
<para>
For example, find the <literal>service=JNDIView</literal> link and click on it. This particular MBean provides a service to allow you to view the structure of the JNDI namespaces within the server. Now find the operation called <literal>list</literal> near the bottom of the MBean view page and click the <literal>invoke</literal> button. The operation returns a view of the current names bound into the JNDI tree, which is very useful when you start deploying your own applications and want to know why you can’t resolve a particular EJB name.
</para>
- <figure id="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application">
+ <!-- <figure id="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application">
<title>View of the JMX Management Console Web Application</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="images/jmx-console.png" />
</imageobject>
</mediaobject>
- </figure>
+ </figure> -->
<para>
Look at some of the other MBeans and their listed operations; try changing some of the configuration attributes and see what happens. With a very few exceptions, none of the changes made through the console are persistent. The original configuration will be reloaded when you restart JBoss, so you can experiment freely without doing any permanent damage.
</para>
@@ -259,7 +259,7 @@
The non-core, hot-deployable services are added to the <filename class="directory">deploy</filename> directory. They can be either XML descriptor files, <filename>*-service.xml, *-jboss-beans.xml</filename>, MC <filename>.beans</filename> archive, or JBoss Service Archive (SAR) files. SARs contains an META-INF/jboss-service.xml descriptor and additional resources the service requires (e.g. classes, library JAR files or other archives), all packaged up into a single archive. Similarly, a <filename>.beans</filename> archive contains a META-INF/jboss-beans.xml and additional resources.
</para>
<para>
- Detailed information on all these services can be found in the <emphasis>JBoss Application Server: Configuration Guide</emphasis>, which also provides comprehensive information on server internals and the implementation of services such as JTA and the J2EE Connector Architecture (JCA).
+ Detailed information on all these services can be found in the <emphasis>JBoss Enterprise Application Platform: Aministration and Configuration Guide</emphasis>, which also provides comprehensive information on server internals and the implementation of services such as JTA and the J2EE Connector Architecture (JCA).
</para>
</section>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -17,7 +17,7 @@
<section id="Using_other_Databases-DataSource_Configuration_Files">
<title>DataSource Configuration Files</title>
<para>
- Datasource configuration file names end with the suffix <literal>-ds.xml</literal> so that they will be recognized correctly by the JCA deployer. The <literal>docs/example/jca</literal> directory contains sample files for a wide selection of databases and it is a good idea to use one of these as a starting point. For a full description of the configuration format, the best place to look is the DTD file <literal>docs/dtd/jboss-ds_1_5.dtd</literal>. Additional documentation on the files and the JBoss JCA implementation can also be found in the JBoss Application Server Guide available at <ulink url="http://labs.jboss.com/projects/docs/"/>.
+ Datasource configuration file names end with the suffix <literal>-ds.xml</literal> so that they will be recognized correctly by the JCA deployer. The <literal>docs/example/jca</literal> directory contains sample files for a wide selection of databases and it is a good idea to use one of these as a starting point. For a full description of the configuration format, the best place to look is the DTD file <literal>docs/dtd/jboss-ds_1_5.dtd</literal>. Additional documentation on the files and the JBoss JCA implementation can also be found in the JBoss Enterprise Application Platform Administration and Server Configuration Guide available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"/>.
</para>
<para>
@@ -29,8 +29,8 @@
<para>
If you look at the example files <literal> firebird-ds.xml</literal>, <literal> facets-ds.xml</literal> and <literal>sap3-ds.xml</literal>, you’ll notice that they have a completely different format, with the root element being <literal>connection-factories</literal> rather than <literal>datasources</literal>. These use an alternative, more generic JCA configuration syntax used with a pre-packaged JCA resource adapter. The syntax is not specific to datasource configuration and is used, for example, in the <literal>jms-ds.xml</literal> file to configure the JMS resource adapter.
</para>
- <para>We would also highly recommend consulting the JCA wiki pages at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJCA
- </para>
+ <!-- <para>We would also highly recommend consulting the JCA wiki pages at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJCA
+ </para> -->
<para>
Next, we’ll work through some step-by-step examples to illustrate what’s involved setting up a datasource for a specific database.
</para>
@@ -263,10 +263,10 @@
ic = new InitialContext();
ds = (DataSource)ic.lookup( "java:/DefaultDS" );
con = ds.getConnection();
- pr = con.prepareStatement("SELECT USERID, PASSWD FROM JMS_USERS");
+ pr = con.prepareStatement("SELECT USER_ID, PASSWD FROM JBM_USER");
ResultSet rs = pr.executeQuery();
while (rs.next()) {
- out.println("<br> " +rs.getString("USERID") + " | " +rs.getString("PASSWD"));
+ out.println("<br> " +rs.getString("USER_ID") + " | " +rs.getString("PASSWD"));
}
rs.close();
pr.close();
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Seam.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Seam.xml 2009-08-13 05:15:28 UTC (rev 92297)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Seam.xml 2009-08-13 05:54:10 UTC (rev 92298)
@@ -12,7 +12,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://docs.jboss.com/seam/2.0.0.GA/reference/en/html_single/">The Seam Reference Guide</ulink>.
+ <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Seam_Reference_Guide/index.html">The Seam Reference Guide</ulink>.
</para>
</listitem>
<listitem>
@@ -389,7 +389,7 @@
</title>
<para>
- This completes our walkthrough of the sample Seam application. For further, detailed information on developing applications using the Seam framework, please refer to the <ulink url="http://docs.jboss.com/seam/2.0.0.GA/reference/en/html_single/">The Seam Reference Guide</ulink>.
+ This completes our walkthrough of the sample Seam application. For further, detailed information on developing applications using the Seam framework, please refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Seam_Reference_Guide/index.html">The Seam Reference Guide</ulink>.
</para>
</section>
</chapter>
More information about the jboss-cvs-commits
mailing list