[jboss-cvs] JBossAS SVN: r92599 - projects/docs/enterprise/5.0/Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Aug 19 23:32:29 EDT 2009
Author: irooskov at redhat.com
Date: 2009-08-19 23:32:29 -0400 (Wed, 19 Aug 2009)
New Revision: 92599
Modified:
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Sample_JSF_EJB3_Application.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:
updated guide
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml 2009-08-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -12,7 +12,7 @@
<xi:include href="Sample_JSF_EJB3_Application.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Using_Seam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Appendix2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Appendix2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
</book>
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-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -15,18 +15,11 @@
<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 Enterprise Application Platform</citetitle> and component <citetitle>Documentation</citetitle>.
+ If you find a typographical error or if you have thought of a way to make this manual better, submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the product <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>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> -->
- </section></preface>
+ </section>
+</preface>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Sample_JSF_EJB3_Application.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Sample_JSF_EJB3_Application.xml 2009-08-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Sample_JSF_EJB3_Application.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -4,7 +4,7 @@
<chapter id="Sample_JSF_EJB3_Application">
<title>Sample JSF-EJB3 Application</title>
<para>
- We use a simple "TODO" application to show how JSF and EJB3 work together in a web application. The "TODO" application works like this: You can create a new 'todo' task item using the "Create" web form. Each 'todo' item has a 'title' and a 'description'. When you submit the form, the application saves your task to a relational database. Using the application, you can view all 'todo' items, edit/delete an existing 'todo' item and update the task in the database.
+ We use a simple <emphasis>TODO</emphasis> application to show how JSF and EJB3 work together in a web application. The <emphasis>TODO</emphasis> application works like this, you can create a new <emphasis>todo</emphasis> task item using the <emphasis>Create</emphasis> web form. Each <emphasis>todo</emphasis> item has a <emphasis>title</emphasis> and a <emphasis>description</emphasis>. When you submit the form, the application saves your task to a relational database. Using the application, you can view all <emphasis>todo</emphasis> items, edit and existing <emphasis>todo</emphasis> item, delete an existing <emphasis>todo</emphasis> item and update the task in the database.
</para>
<para>
The sample application comprises the following components:
@@ -29,10 +29,10 @@
<section id="Sample_JSF_EJB3_Application-Data_Model">
<title>Data Model</title>
<para>
- Let's take a look at the contents of the Data Model represented by the <literal>Todo</literal> class in the <literal>Todo.java</literal> file. Each instance of the <literal>Todo</literal> class corresponds to a row in the relational database table. The 'Todo' class has three properties: id, title and description. Each of these correspond to a column in the database table.
+ Let's take a look at the contents of the Data Model represented by the <literal>Todo</literal> class in the <literal>Todo.java</literal> file. Each instance of the <literal>Todo</literal> class corresponds to a row in the relational database table. The <literal>Todo</literal> class has three properties: <property>ID</property>, <property>title</property> and <property>description</property>. Each of these correspond to a column in the database table.
</para>
<para>
- The 'Entity class' to 'Database Table' mapping information is specified using EJB3 Annotations in the 'Todo' class. This eliminates the need for XML configuration and makes it a lot clearer. The <literal>@Entity</literal> annotation defines the <literal>Todo</literal> class as an Entity Bean. The <literal>@Id</literal> and <literal>@GeneratedValue</literal> annotations on the <literal>id</literal> property indicate that the <literal>id</literal> column is the primary key and that the server automatically generates its value for each <literal>Todo</literal> object saved into the database.
+ The <emphasis>Entity class</emphasis> to <emphasis>Database Table</emphasis> mapping information is specified using EJB3 Annotations in the <literal>Todo</literal> class. This eliminates the need for XML configuration and makes it a lot clearer. The <literal>@Entity</literal> annotation defines the <literal>Todo</literal> class as an Entity Bean. The <literal>@Id</literal> and <literal>@GeneratedValue</literal> annotations on the <literal>id</literal> property indicate that the <literal>id</literal> column is the primary key and that the server automatically generates its value for each <literal>Todo</literal> object saved into the database.
</para>
<para>
<programlisting>
@@ -67,11 +67,11 @@
<section id="Sample_JSF_EJB3_Application-JSF_Web_Pages">
<title>JSF Web Pages</title>
<para>
- In this section we will show you how the web interface is defined using JSF pages. We will also see how the data model is mapped to the web form using JSF EL. Using the #{...} notation to reference Java objects is called <emphasis role="bold">JSF EL</emphasis> (JSF Expression Language). Lets take a look at the pages used in our application:
+ In this section we will show you how the web interface is defined using JSF pages. We will also see how the data model is mapped to the web form using JSF EL. Using the <code>#{...}</code> notation to reference Java objects is called <emphasis role="bold">JSF EL</emphasis> (JSF Expression Language). Lets take a look at the pages used in our application:
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">index.xhtml</emphasis>: This page displays two options: 1. Create New Todo 2. Show all Todos. When you click on the Submit button the corresponding action is invoked.
+ <filename>index.xhtml</filename>: This page displays two options: 1. Create New Todo 2. Show all Todos. When you click on the Submit button the corresponding action is invoked.
</para>
<para>
<programlisting>
@@ -298,7 +298,7 @@
<para>Let's look at building the example application and then explore the configuration files in detail.
</para>
<para>
- In <xref linkend="About_the_Example_Applications"/>, we looked at the directory structure of the <literal>jsfejb3</literal> sample application. At the command line, go to the <literal>jsfejb3</literal> directory. There you will see a <literal>build.xml</literal> file. This is our Ant build script for compiling and packaging the archives. To build the application, you need to first of all edit the <literal>build.xml</literal> file and edit the value of <literal>jboss-dist</literal> to reflect the location where the JBoss Application Server is installed. Once you have done this, just type the command <literal>ant</literal> and your output should look like this:
+ In <xref linkend="About_the_Example_Applications"/>, we looked at the directory structure of the <literal>jsfejb3</literal> sample application. At the command line, go to the <literal>jsfejb3</literal> directory. There you will see a <literal>build.xml</literal> file. This is our Ant build script for compiling and packaging the archives. To build the application, you need to first of all edit the <literal>build.xml</literal> file and set the <varname>JBOSS_HOME</varname> environment property to reflect the location where the JBoss Enterprise Application Platform server is installed. Once you have done this, just type the command <literal>ant</literal> and your output should look like this:
</para>
<screen>[user at localhost jsfejb3]$ ant
Buildfile: build.xml
@@ -337,17 +337,17 @@
<emphasis role="bold">jars</emphasis>: containing three archives - <literal>app.jar</literal>, <literal>app.war</literal> and <literal>jsfejb3.ear</literal>. <itemizedlist>
<listitem>
<para>
- app.jar : EJB code and descriptors.
+ <filename>app.jar</filename>: EJB code and descriptors.
</para>
</listitem>
<listitem>
<para>
- app.war : web application which provides the front end to allow users to interact with the business components (the EJBs). The web source (HTML, images etc.) contained in the <literal>jsfejb3/view</literal> directory is added unmodified to this archive. The Ant task also adds the <literal>WEB-INF</literal> directory that contains the files which aren’t meant to be directly accessed by a web browser but are still part of the web application. These include the deployment descriptors (<literal>web.xml</literal>) and extra jars required by the web application.
+ <filename>app.war</filename>: web application which provides the front end to allow users to interact with the business components (the EJBs). The web source (HTML, images etc.) contained in the <literal>jsfejb3/view</literal> directory is added unmodified to this archive. The Ant task also adds the <literal>WEB-INF</literal> directory that contains the files which aren’t meant to be directly accessed by a web browser but are still part of the web application. These include the deployment descriptors (<literal>web.xml</literal>) and extra jars required by the web application.
</para>
</listitem>
<listitem>
<para>
- jsfejb3.ear : The EAR file is the complete application, containing the EJB modules and the web module. It also contains an additional descriptor, <literal>application.xml</literal>. It is also possible to deploy EJBs and web application modules individually but the EAR provides a convenient single unit.
+ <filename>jsfejb3.ear</filename>: The EAR file is the complete application, containing the EJB modules and the web module. It also contains an additional descriptor, <literal>application.xml</literal>. It is also possible to deploy EJBs and web application modules individually but the EAR provides a convenient single unit.
</para>
</listitem>
</itemizedlist>
@@ -465,7 +465,7 @@
<section id="The_Database-Creating_the_Database_Schema">
<title>Creating the Database Schema</title>
<para>
- To pre-populate the database, we have supplied SQL Code (<literal>import.sql</literal>) to run with HSQL in the <literal>examples/jsfejb3/resources</literal> directory. When you build the application using Ant, this is packaged in the app.jar file within the jsfejb3.ear file. When the application is deployed, you should be able to view the pre-populated data.
+ To pre-populate the database, we have supplied SQL Code (<literal>import.sql</literal>) to run with HSQL in the <literal>examples/jsfejb3/resources</literal> directory. When you build the application using ANT, this is packaged in the <filename>app.jar</filename> file within the <filename>jsfejb3.ear</filename> file. When the application is deployed, you should be able to view the pre-populated data.
</para>
</section>
<section id="The_Database-The_HSQL_Database_Manager_Tool">
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-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -4,7 +4,7 @@
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations">
<title>Server Configurations</title>
<para>
- Fundamentally, the JBoss architecture consists of the microcontainer, bootstrap beans loaded into the micrcontainer, a collection of deployers for loading various deployment types, and various mcbean(-jboss-beans.xml) and legacy mbean(jboss-service.xml) deployments.
+ Fundamentally, the JBoss architecture consists of the microcontainer, bootstrap beans loaded into the micrcontainer, a collection of deployers for loading various deployment types, and various mcbean(<filename>-jboss-beans.xml</filename>) and legacy mbean(<filename>jboss-service.xml</filename>) deployments.
This makes it easy to assemble different configurations and gives you the flexibility to tailor them to meet your requirements.
</para>
<para>
@@ -39,7 +39,7 @@
<term>production</term>
<listitem>
<para>
- 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.
+ is based on the <literal>all</literal> 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>
@@ -47,7 +47,7 @@
<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.
+ 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>
@@ -516,7 +516,7 @@
<literal>bindingservice.beans/*</literal>
</entry>
<entry>
- This directory contains the configurations for various ports used by the server. See section [TODO: Point to the section which explains about port configurations] for details about port configurations.
+ This directory contains the configurations for various ports used by the server.
</entry>
</row>
<row>
@@ -681,7 +681,7 @@
<literal>dependency-deployers-jboss-beans.xml</literal>
</entry>
<entry>
- Deployers for aliases.txt, jboss-dependency.xml jboss-depedency.xml adds generic dependency on whatever. aliases.txt adds human-readable name for deployments, e.g. vfszip://home/blah/.../jboss-5.0.0.GA/server/default/deploy/some-long-name.ear aliased to ales-app.ear.
+ Deployers for <filename>aliases.txt</filename> and <filename>jboss-dependency.xml</filename>. <filename>jboss-depedency.xml</filename> adds generic dependency and <filename>aliases.txt</filename> adds human-readable names for deployments. For instance, <filename>vfszip://home/something/.../jboss-5.0.0.GA/server/default/deploy/some-long-name.ear</filename> aliased to <filename>ales-app.ear</filename>.
</entry>
</row>
<row>
@@ -689,8 +689,7 @@
<literal>directory-deployer-jboss-beans.xml</literal>
</entry>
<entry>
- Adds legacy behavior for directories, handling its children as possible deployments.
- e.g. .sar's lib directory to treat its .jar files as deployments
+ Adds legacy behavior for directories, handling its children as possible deployments. For example, <filename>.sar</filename>'s <filename>lib</filename> directory to treat the <filename>.jar</filename> files as deployments.
</entry>
</row>
<row>
@@ -722,7 +721,7 @@
<literal>hibernate-deployer-jboss-beans.xml</literal>
</entry>
<entry>
- Deployers for Hibernate -hibernate.xml descriptors, which are similar to Hibernate's .cfg.xml files.
+ Deployers for Hibernate -hibernate.xml descriptors, which are similar to Hibernate's <filename>.cfg.xml</filename> files.
</entry>
</row>
<row>
@@ -730,7 +729,7 @@
<literal>jboss-aop-jboss5.deployer</literal>
</entry>
<entry>
- JBossAspectLibrary and base aspects. Why is this in deployers, dependencies?
+ JBossAspectLibrary and base aspects.
</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-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -18,7 +18,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.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_And_Configuration_Guide/index.html">Administration and Configuration Guide</ulink>.
</para>
<para>
@@ -43,10 +43,10 @@
</programlisting>
-<para>More options for the JBoss AS <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/> below.</para>
+<para>More options for the JBoss Enterprise Application Platform <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/> below.</para>
<note>
<para>
- Note that there is no "Server Started" 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 may be observed in the <filename>server.log</filename> file located in the <filename class="directory">server/production/log</filename> subdirectory.
+ Note that there is no <emphasis>Server Started</emphasis> 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 may be observed in the <filename>server.log</filename> file located in the <filename class="directory">server/production/log</filename> subdirectory.
</para>
</note>
</section>
@@ -54,7 +54,7 @@
<section id="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration">
<title>Start the Server With Alternate Configuration</title>
<para>
- Using <literal>run.sh</literal> without any arguments starts the server using the <literal>production</literal> server configuration file set. To start with an alternate configuration file set, pass the name of the server configuration file set [same as the name of the server configuration directory under <literal>JBOSS_DIST/jboss-as/server</literal>] that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>minimal</literal> configuration file set you should specify:
+ Using <literal>run.sh</literal> without any arguments starts the server using the <literal>production</literal> server configuration file set. To start with an alternate configuration file set, pass the name of the server configuration file set (same as the name of the server configuration directory under <literal>JBOSS_DIST/jboss-as/server</literal>) that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>minimal</literal> configuration file set you should specify:
</para>
<programlisting>[bin]$ ./run.sh -c minimal
...
@@ -95,7 +95,7 @@
<section id="Starting_and_Stopping_the_Server-Stopping_the_Server">
<title>Stopping the Server</title>
<para>
- To shutdown the server, you simply issue a Ctrl-C sequence in the console in which JBoss was started. Alternatively, you can use the <literal>shutdown.sh</literal> command.
+ To shutdown the server, you simply issue a <literal>Ctrl-C</literal> sequence in the console in which JBoss was started. Alternatively, you can use the <literal>shutdown.sh</literal> command.
</para>
<programlisting>[bin]$ ./shutdown.sh -S</programlisting>
<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-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -251,7 +251,7 @@
There are 6 basic log levels used: <literal>TRACE</literal>, <literal>DEBUG</literal>, <literal>INFO</literal>, <literal>WARN</literal>, <literal>ERROR</literal> and <literal>FATAL</literal>. The logging threshold on the console is <literal>INFO</literal>, which means that you will see informational messages, warning messages and error messages on the console but not general debug and trace messages. In contrast, there is no threshold set for the <filename>server.log</filename> file, so all generated logging messages will be logged there.
</para>
<para>
- If things are going wrong and there doesn’t seem to be any useful information in the console, always check the <filename>server.log</filename> file to see if there are any debug messages which might help you to track down the problem. However, be aware that just because the logging threshold allows debug messages to be displayed, that doesn't mean that all of JBoss will produce detailed debug information for the log file. You will also have to boost the logging limits set for individual categories. Take the following category for example.
+ If things are going wrong and there doesn’t seem to be any useful information in the console, always check the <filename>server.log</filename> file to see if there are any debug messages which might help you to track down the problem. However, be aware that just because the logging threshold allows debug messages to be displayed, that doesn't mean that all of JBoss will produce detailed debug information for the log file. You will also have to boost the logging limits set for individual categories. Take the following category for example.
</para>
<programlisting><!-- Limit JBoss categories to INFO -->
<category name="org.jboss">
@@ -377,7 +377,7 @@
</security-constraint>
</programlisting>
<para>
- That's great, but where do the user names and passwords come from? They come from the <literal>jmx-console</literal> security domain we linked the application to. We have provided the configuration for this in the <filename>conf/login-config.xml</filename>.
+ That's great, but where do the user names and passwords come from? They come from the <literal>jmx-console</literal> security domain we linked the application to. We have provided the configuration for this in the <filename>conf/login-config.xml</filename>.
</para>
<para>
<programlisting><application-policy name="jmx-console">
@@ -412,7 +412,7 @@
<section id="Basic_Configuration_Issues-Additional_Services">
<title>Additional Services</title>
<para>
- 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.
+ 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 <filename>META-INF/jboss-service.xml</filename> descriptor and additional resources the service requires (for example, classes, library JAR files or other archives), all packaged up into a single archive. Similarly, a <filename>.beans</filename> archive contains a <filename>META-INF/jboss-beans.xml</filename> and additional resources.
</para>
<para>
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).
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-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -5,7 +5,7 @@
<chapter id="Using_other_Databases">
<title>Using other Databases</title>
<para>
- In the previous chapters, we’ve been using the JBossAS default datasource in our applications. This datasource is configured to use the embedded Hypersonic database instance shipped by default with the distribution. This datasource is bound to the JNDI name <literal>java:/DefaultDS</literal> and its descriptor is named <literal>hsqldb-ds.xml</literal> under the deploy directory
+ In the previous chapters, we’ve been using the JBoss Enterprise Application Platform server default datasource in our applications. This datasource is configured to use the embedded Hypersonic database instance shipped by default with the distribution. This datasource is bound to the JNDI name <literal>java:/DefaultDS</literal> and its descriptor is named <literal>hsqldb-ds.xml</literal> under the deploy directory
</para>
<para>
Having a database included with JBoss Enterprise Application Platform is very convenient for running the server and examples out-of-the-box. However, this database is not a production quality database and as such should not be used with enterprise-class deployments. As a consequence of this JBoss Support does not provide any official support for Hypersonic.
@@ -147,7 +147,7 @@
<section id="Setting_up_an_XADataSource_with_Oracle_9i-Installing_the_JDBC_Driver_and_Deploying_the_DataSource">
<title>Installing the JDBC Driver and Deploying the DataSource</title>
<para>
- To make the JDBC driver classes available to JBoss Application Server, copy the archive ojdbc5.jar to the lib directory in the default server configuration (assuming that is the server configuration you’re running).
+ To make the JDBC driver classes available to the JBoss Enterprise Application Platform, copy the archive <filename>ojdbc5.jar</filename> to the lib directory in the default server configuration (assuming that is the server configuration you’re running).
</para>
<para>
Then create a text file in the <filename>deploy</filename> directory called <filename>oracle-ds.xml</filename> with the following datasource descriptor :
@@ -169,7 +169,7 @@
</datasources></programlisting>
<para>
- The datasource is pointing at the database/SID called “xe” provided by default with Oracle XE.
+ The datasource is pointing at the database/SID called <emphasis>xe</emphasis> provided by default with Oracle XE.
</para>
<para>
Of course, you need to update the connection url attributes as well as the username/password combination to match your environment setup.
@@ -190,7 +190,7 @@
<section id="Setting_up_an_XADataSource_with_Oracle_9i-Testing_the_Oracle_DataSource">
<title>Testing the Oracle DataSource</title>
<para>
- Before you can verify the datasource configuration, Oracle XE should be reconfigured to avoid port conflict with JBossAS as by default they both start a web server on port 8080.
+ Before you can verify the datasource configuration, Oracle XE should be reconfigured to avoid port conflict with the JBoss Enterprise Application Platform as by default they both start a web server on port 8080.
</para>
<para>Open up an Oracle SQLcommand line and execute the following commands:
</para>
@@ -212,7 +212,7 @@
<para>
The web server started by Oracle XE to provide http-based administration tools is now running on port 8090.
- Start the JBossAS server instance as you would normally do. You are now ready to use the test client described in Chapter 6.5 to verify the proper installation of your datasource.
+ Start the JBoss Enterprise Application Platform server instance as you would normally do. You are now ready to use the test client to verify the proper installation of your datasource.
</para>
</section>
@@ -225,7 +225,7 @@
<section><title>Installing the JDBC Driver and Deploying the DataSource</title>
<para>
- To make the JDBC driver classes available to JBoss Application Server, copy the archive <filename>sqljdbc.jar</filename> from the <filename>sqljdbc_1.2</filename> distribution to the <filename>lib</filename> directory in the default server configuration (assuming that is the server configuration you’re running).
+ To make the JDBC driver classes available to the JBoss Enterprise Application Platform, copy the archive <filename>sqljdbc.jar</filename> from the <filename>sqljdbc_1.2</filename> distribution to the <filename>lib</filename> directory in the default server configuration (assuming that is the server configuration you’re running).
</para>
<para>
Then create a text file in the <literal>deploy</literal> directory called <literal>mssql-ds.xml</literal> with the following datasource descriptor :
@@ -246,7 +246,7 @@
</datasources> ]]>
</programlisting>
-The datasource is pointing at a database “pubs” provided by default with MS SQL Server 2000.
+The datasource is pointing at a database <literal>pubs</literal> provided by default with MS SQL Server 2000.
</para>
<para>
Remember to update the connection url attributes as well as the username/password combination to match your environment setup.
@@ -263,7 +263,7 @@
<section id="configuring_jbossmessaging_persistence_manager"><title>Configuring JBoss Messaging Persistence Manager</title>
<para>
- The persistence manager of JBoss Messaging uses the default datasource to create tables to store messages, transaction data and other indexes. Configuration of "persistence" is grouped in <filename>xxx-persistence-service.xml</filename> files. JBoss Application Server ships with a default <filename>hsqldb-persistence-service.xml</filename> file, which configures the Messaging server to use the Hypersonic database instance that ships by default with the JBoss Application Server.
+ The persistence manager of JBoss Messaging uses the default datasource to create tables to store messages, transaction data and other indexes. Configuration of "persistence" is grouped in <filename>xxx-persistence-service.xml</filename> files. JBoss Enterprise Application Platform ships with a default <filename>hsqldb-persistence-service.xml</filename> file, which configures the Messaging server to use the Hypersonic database instance that ships by default with the JBoss Enterprise Application Platform.
</para>
<para>
You can view the <filename>hsqldb-persistence-service.xml</filename> file in configurations based on the <emphasis>all</emphasis> or <emphasis>default</emphasis> configurations:
@@ -275,11 +275,11 @@
<warning><title>Warning</title>
- <para>Please note that the Hypersonic database is not recommended for production environments due to its limited support for transaction isolation and its low reliability under high load</para>
+ <para>The Hypersonic database is not recommended for production environments due to its limited support for transaction isolation and its low reliability under high load</para>
</warning>
<para>
- More information on configuring JBoss Messaging can be found in the <ulink url="http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta500/html-single/index.html#d0e3471">JBoss AS Configuration Guide</ulink>.
+ More information on configuring JBoss Messaging can be found in the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_And_Configuration_Guide/index.html">Administration and Configuration Guide</ulink>.
</para>
@@ -322,7 +322,7 @@
}]]> %> </programlisting>
Open up a web browser and hit the url: <ulink url="http://localhost:8080/jdbcclient/client.jsp"/>.
-A list of users and password should show up as a result of the jdbc query:
+A list of users and password should show up as a result of the JDBC query:
<screen>
dynsub | dynsub
guest | guest
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-20 02:01:53 UTC (rev 92598)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Seam.xml 2009-08-20 03:32:29 UTC (rev 92599)
@@ -97,7 +97,7 @@
<section id="Using_Seam_JSF_Web_Pages">
<title>
- JSF Web Pages - index.xhtml and create.xhtml
+ JSF Web Pages: index.xhtml and create.xhtml
</title>
<para>
@@ -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://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>.
+ 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