[jboss-cvs] JBossAS SVN: r78975 - in projects/docs/community/5/Installation_And_Getting_Started_Guide: en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 30 22:03:48 EDT 2008
Author: skittoli at redhat.com
Date: 2008-09-30 22:03:46 -0400 (Tue, 30 Sep 2008)
New Revision: 78975
Removed:
projects/docs/community/5/Installation_And_Getting_Started_Guide/target/
projects/docs/community/5/Installation_And_Getting_Started_Guide/tmp/
Modified:
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/EJB3_Caveats.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Installation_Using_Graphical_Installer.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Preface.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Using_Other_Databases.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml
Log:
removed tmp and target dirs
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/EJB3_Caveats.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/EJB3_Caveats.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/EJB3_Caveats.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -17,7 +17,7 @@
</title>
<para>
- The Release Notes for JBoss Application Server 4.0.0 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 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.
</para>
</section>
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Installation_Using_Graphical_Installer.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Installation_Using_Graphical_Installer.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Installation_Using_Graphical_Installer.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -138,7 +138,7 @@
</listitem>
<listitem>
<para>
- You are done with the installation! You should now have a directory called <filename>jboss-4.2.2.GA</filename>, or whatever other name you specified. To explore the Server directory structure and to understand the layout in detail, refer to the Getting Started Guide.
+ You are done with the installation! You should now have a directory called <filename>jboss-<version></filename>, or whatever other name you specified.
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Preface.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Preface.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -12,7 +12,7 @@
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.
</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 uninstall JBoss.</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>
<xi:include href="Software_Versions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</preface>
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -8,7 +8,7 @@
<section id="setting_JBOSS_HOME_linux"><title>Setting the <command>JBOSS_HOME</command> variable in Linux.</title>
<para>
- Before you can run the JBoss Application Server, you need to ensure that you've configured the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file as follows. In this example the Application Server folder has beeen copied to the <filename>/usr/jboss/jboss-5.0.0.<release></filename> folder.
+ Before you can run the JBoss Application Server, you need to ensure that you've configured the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file as follows. In this example the Application Server folder has beeen copied to the <filename>/usr/jboss/jboss-<release></filename> folder.
The following is a <filename>.bashrc</filename> file used in this installation. Please ensure that your <filename>.bashrc</filename> file has a similar configuration.
<screen>[user at localhost ~]$ gedit .bashrc
@@ -21,13 +21,13 @@
# User specific aliases and functions
# The following are the environment variables for Java, ANT and JBoss
-export JAVA_HOME=/usr/java/jdk1.5.0_14
+export JAVA_HOME=/usr/java/jdk1.6.0_07
export PATH=$PATH:$JAVA_HOME/bin
export ANT_HOME=/usr/ant/apache-ant-1.6.0
export PATH=$PATH:$ANT_HOME/bin
-export JBOSS_HOME=/usr/jboss/jboss-5.0.0.<release>
+export JBOSS_HOME=/usr/jboss/jboss-<release>
export PATH=$PATH:$JBOSS_HOME/bin
</screen>
@@ -46,16 +46,16 @@
<itemizedlist>
<listitem>
<para>
- Create an environment variable called <literal>JBOSS_HOME</literal> that points to the JBoss Application Server installation directory, for example: <literal>C:\Program Files\JBoss\jboss-5.0.0.<release>\</literal>.
+ Create an environment variable called <literal>JBOSS_HOME</literal> that points to the JBoss Application Server installation directory, for example: <literal>C:\Program Files\JBoss\jboss-<release>\</literal>.
</para>
</listitem>
<listitem>
<para>
- In order to run JBoss Application Server from the command line, add the <literal>jboss-5.0.0.<release>\bin</literal> directory to your path, for example: <literal>C:\Program Files\JBoss\jboss-5.0.0.<release>\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
+ In order to run JBoss Application Server from the command line, add the <literal>jboss-<release>\bin</literal> directory to your path, for example: <literal>C:\Program Files\JBoss\jboss-<release>\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
</para>
</listitem>
</itemizedlist>
- You are now ready to start the JBoss Application Server. For more information on starting or stopping the server, please refer to <ulink url="http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/Getting_Started_Guide/beta500/html-single/index.html#Starting_and_Stopping_the_Server">Getting Started Guide</ulink>.
+ You are now ready to start the JBoss Application Server.
</para>
</section>
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -27,14 +27,14 @@
JBoss Bootstrap Environment
- JBOSS_HOME: /home/user/jboss-as-5.0.0/jboss-as
+ JBOSS_HOME: /home/user/jboss-as-version/jboss-as
JAVA: java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.client.
gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
- CLASSPATH: /home/user/jboss-as-5.0.0/jboss-as/bin/run.jar
+ CLASSPATH: /home/user/jboss-as-version/jboss-as/bin/run.jar
=========================================================================
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -139,7 +139,7 @@
This creates a new file appender and specifies that it should be used by the logger (or category) for the package <literal>org.jboss.ejb.plugins.cmp</literal>.
</para>
<para>
- The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to the name. You will notice that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
+ The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to their filenames. Please note that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
</para>
</section>
@@ -149,7 +149,7 @@
The security domain information is stored in the file <filename>conf/login-config.xml</filename> as a list of named security domains, each of which specifies a number of JAAS <footnote><para>
The Java Authentication and Authorization Service. JBoss uses JAAS to provide pluggable authentication modules. You can use the ones that are provided or write your own if you have more specific requirements.
</para>
- </footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application that ship with JBoss.
+ </footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application which ships with JBoss.
</para>
<para>
Almost every aspect of the JBoss server can be controlled through the JMX Console, so it is important to make sure that, at the very least, the application is password protected. Otherwise, any remote user could completely control your server. To protect it, we will add a security domain to cover the application.
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Using_Other_Databases.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Using_Other_Databases.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Using_Other_Databases.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -5,10 +5,10 @@
<chapter id="Using_other_Databases">
<title>Using other Databases</title>
<para>
- In the previous chapters, we’ve just 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 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
</para>
<para>
- Having a database included with JBossAS 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.
+ Having a database included with JBossAS 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.
</para>
<para>
In this chapter we will explain in details how to configure and deploy a datasource to connect JBossAS to the most popular database servers available on the market today.
@@ -57,23 +57,20 @@
Then create a text file in the deploy directory called mysql-ds.xml with the following datasource descriptor:
</para>
-<programlisting> <![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<datasources>
- <local-tx-datasource>
- <jndi-name>DefaultDS</jndi-name>
- <connection-url>jdbc:mysql://localhost:3306/test</connection-url>
- <driver-class>com.mysql.jdbc.Driver</driver-class>
- <user-name>root</user-name>
- <password>jboss</password>
- <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
- <metadata>
- <type-mapping>mySQL</type-mapping>
- </metadata>
- </local-tx-datasource>
-</datasources>
-]]>
-</programlisting>
+<programlisting role="XML"><?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/test</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name>root</user-name>
+ <password>jboss</password>
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
+ <metadata>
+ <type-mapping>mySQL</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources></programlisting>
<para>
The datasource is pointing at the database called test provided by default with MySQL 5.x.
@@ -83,29 +80,6 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<section id="Using_MySQL_as_the_Default_DataSource-Testing_the_MySQL_DataSource">
<title>Testing the MySQL DataSource</title>
<para>
@@ -134,25 +108,24 @@
</para>
<para>
Then create a text file in the <filename>deploy</filename> directory called <filename>oracle-ds.xml</filename> with the following datasource descriptor :
+ </para>
- <programlisting><![CDATA[
- <?xml version="1.0" encoding="UTF-8"?>
- <datasources>
- <local-tx-datasource>
- <jndi-name>DefaultDS</jndi-name>
- <connection-url>jdbc:oracle:thin:@localhost:1521:xe</connection-url>
- <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
- <user-name>SYSTEM</user-name>
- <password>jboss</password>
- <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
- <metadata>
- <type-mapping>Oracle9i</type-mapping>
- </metadata>
- </local-tx-datasource>
- </datasources>
- ]]>
- </programlisting>
-
+<programlisting role="XML"><?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:oracle:thin:@localhost:1521:xe</connection-url>
+ <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
+ <user-name>SYSTEM</user-name>
+ <password>jboss</password>
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
+ <metadata>
+ <type-mapping>Oracle9i</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources></programlisting>
+
+ <para>
The datasource is pointing at the database/SID called “xe” provided by default with Oracle XE.
</para>
<para>
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -1004,7 +1004,7 @@
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.
</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 uninstall JBoss.</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>
<section id="Software_Versions">
<title>Software Versions</title>
<para>
@@ -1030,18 +1030,18 @@
<section id="Book-We_Need_Feedback">
<title>Help Contribute</title>
<para>
- If you find a typographical error in the <citetitle>Installation 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/jira/secure/IssueNavigator.jspa?reset=true&&pid=10030&resolution=-1&component=12311310&sorter/field=priority&sorter/order=DESC">http://jira.jboss.com</ulink> against the project <citetitle>JBoss Application Server</citetitle> and component <citetitle>Documentation</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 Application Server</citetitle> and component <citetitle>Docs/Installation and Getting Started Guide</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/trunk 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/trunk --username yourname
+ svn co https://svn.jboss.org/repos/jbossas/projects/docs/community/5 --username yourusername
</screen>
</section>
</preface>
@@ -1239,7 +1239,7 @@
When you install from the installer, you get a smaller install image that is more tuned for your environment. However, the directory structure will be slightly different than when using the rpm/zip archive.
</para>-->
<para>
- Four types of server configurations will be included in your installation - <emphasis>minimal</emphasis>, <emphasis>default</emphasis>, and <emphasis>all</emphasis>. The Getting Started Guide explains in detail the different server configuration file sets.
+ Four types of server configurations will be included in your installation - <emphasis>minimal</emphasis>, <emphasis>default</emphasis>, and <emphasis>all</emphasis>.
</para>
</chapter>
<chapter id="binary_installation">
@@ -1257,15 +1257,15 @@
<itemizedlist>
<listitem>
<para>
- Unzip <literal>jboss-4.2.2.GA.zip</literal> to extract the archive contents into the location of your choice. You can do this using the JDK <literal>jar</literal> tool (or any other ZIP extraction tool). In the example below we are assuming you downloaded the zip file to the <filename>/jboss</filename> directory.
+ Unzip <literal>jboss-<release>.zip</literal> to extract the archive contents into the location of your choice. You can do this using the JDK <literal>jar</literal> tool (or any other ZIP extraction tool). In the example below we are assuming you downloaded the zip file to the <filename>/jboss</filename> directory.
<programlisting>
[usr]$ <literal>cd /jboss</literal>
-[usr]$ <literal>jar -xvf jboss-4.2.2.GA.zip</literal></programlisting>
+[usr]$ <literal>jar -xvf jboss-<release>.zip</literal></programlisting>
</para>
</listitem>
<listitem>
<para>
- You should now have a directory called <filename>jboss-4.2.2.GA</filename>. Next you need to set your JBOSS_HOME environment variables. This is discussed in <xref linkend="setting_JBOSS_HOME"/>.
+ You should now have a directory called <filename>jboss-<release></filename>. Next you need to set your JBOSS_HOME environment variables. This is discussed in <xref linkend="setting_JBOSS_HOME"/>.
</para>
</listitem>
</itemizedlist>
@@ -1286,16 +1286,16 @@
<itemizedlist>
<listitem>
<para>
- Uncompress <literal>jboss-5.0.0.<release>-src.tar.gz</literal> to extract the archive contents into the location of your choice. You can do this using the <literal>tar</literal> archiving utility in Linux (or any other compatible extraction tool). In this example we are assuming your source files were copied in the <filename>/jboss</filename> folder.
+ Uncompress <literal>jboss-<release>-src.tar.gz</literal> to extract the archive contents into the location of your choice. You can do this using the <literal>tar</literal> archiving utility in Linux (or any other compatible extraction tool). In this example we are assuming your source files were copied in the <filename>/jboss</filename> folder.
<screen>[user at localhost]$ cd /jboss
-[user at localhost]$ tar -xvf <literal>jboss-5.0.0.<release>-src.tar.gz</literal></screen>
+[user at localhost]$ tar -xvf <literal>jboss-<release>-src.tar.gz</literal></screen>
</para>
</listitem>
<listitem>
<para>
- You should now have a directory called <literal>jboss-5.0.0.<release>-src.tar.gz</literal>. The next step is to build your source files. In this example we are using Apache ANT. This is discussed in the following section.
+ You should now have a directory called <literal>jboss-<release>-src.tar.gz</literal>. The next step is to build your source files. In this example we are using Apache ANT. This is discussed in the following section.
</para>
</listitem>
</itemizedlist>
@@ -1349,7 +1349,7 @@
<para>
To build the JBoss Application Server source files with Apache ANT, from a terminal change directory to where the unzipped source files are. In the following example we are assuming that the source files were copied and unzipped in the logged in user's <filename>downloads</filename> folder.
-<screen>[user at localhost]$ cd /home/user/downloads/<literal>jboss-5.0.0.<release>-src</literal>/build
+<screen>[user at localhost]$ cd /home/user/downloads/<literal>jboss-<release>-src</literal>/build
[user at localhost build]$ ls
build.bat build.log build.sh build.xml eclipse.psf local.properties VersionRelease.java
build-distr.xml build-release.xml build-thirdparty.xml docs etc output
@@ -1359,8 +1359,8 @@
<screen>[user at localhost build]$ ant
compile-classes:
-[mkdir] Created dir: /jboss/jboss-5.0.0.<release>-src/tomcat/output/classes
-[javac] Compiling 89 source files to /jboss/jboss-5.0.0.<release>-src/tomcat/output/classes
+[mkdir] Created dir: /jboss/jboss-<release>-src/tomcat/output/classes
+[javac] Compiling 89 source files to /jboss/jboss-<release>-src/tomcat/output/classes
....
....content truncated
.....
@@ -1372,18 +1372,18 @@
BUILD SUCCESSFUL
Total time: 2 seconds</screen>
-A successful build will have the above message. If your build fails, please check the error log and ensure that your configuration files and environment variables are correctly set. The JBoss Application Server files are built under the <filename>build/jboss-5.0.0.<release></filename> directory as indicated below.
+A successful build will have the above message. If your build fails, please check the error log and ensure that your configuration files and environment variables are correctly set. The JBoss Application Server files are built under the <filename>build/jboss-<release></filename> directory as indicated below.
<screen>[user at localhost build]$ ls
-build.bat build.log build.sh build.xml eclipse.psf jboss-5.0.0.<release> local.properties VersionRelease.java
-build-distr.xml build-release.xml build-thirdparty.xml docs etc outputjboss-5.0.0.<release>
+build.bat build.log build.sh build.xml eclipse.psf jboss-<release> local.properties VersionRelease.java
+build-distr.xml build-release.xml build-thirdparty.xml docs etc outputjboss-<release>
-[user at localhost build]$ cd jboss-5.0.0.<release>
+[user at localhost build]$ cd jboss-<release>
[user at localhost build]$ ls
bin client docs lib server
</screen>
- The <filename>jboss-5.0.0.<release></filename> directory contains your successful JBoss Application Server files. You can copy this folder to a different location or run the server from this folder after setting the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file. Next you need to set your JBOSS_HOME environment variables. This is discussed in <xref linkend="setting_JBOSS_HOME"/>.
+ The <filename>jboss-<release></filename> directory contains your successful JBoss Application Server files. You can copy this folder to a different location or run the server from this folder after setting the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file. Next you need to set your JBOSS_HOME environment variables. This is discussed in <xref linkend="setting_JBOSS_HOME"/>.
</para>
</section>
@@ -1398,7 +1398,7 @@
<section id="setting_JBOSS_HOME_linux"><title>Setting the <command>JBOSS_HOME</command> variable in Linux.</title>
<para>
- Before you can run the JBoss Application Server, you need to ensure that you've configured the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file as follows. In this example the Application Server folder has beeen copied to the <filename>/usr/jboss/jboss-5.0.0.<release></filename> folder.
+ Before you can run the JBoss Application Server, you need to ensure that you've configured the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file as follows. In this example the Application Server folder has beeen copied to the <filename>/usr/jboss/jboss-<release></filename> folder.
The following is a <filename>.bashrc</filename> file used in this installation. Please ensure that your <filename>.bashrc</filename> file has a similar configuration.
<screen>[user at localhost ~]$ gedit .bashrc
@@ -1411,13 +1411,13 @@
# User specific aliases and functions
# The following are the environment variables for Java, ANT and JBoss
-export JAVA_HOME=/usr/java/jdk1.5.0_14
+export JAVA_HOME=/usr/java/jdk1.6.0_07
export PATH=$PATH:$JAVA_HOME/bin
export ANT_HOME=/usr/ant/apache-ant-1.6.0
export PATH=$PATH:$ANT_HOME/bin
-export JBOSS_HOME=/usr/jboss/jboss-5.0.0.<release>
+export JBOSS_HOME=/usr/jboss/jboss-<release>
export PATH=$PATH:$JBOSS_HOME/bin
</screen>
@@ -1436,16 +1436,16 @@
<itemizedlist>
<listitem>
<para>
- Create an environment variable called <literal>JBOSS_HOME</literal> that points to the JBoss Application Server installation directory, for example: <literal>C:\Program Files\JBoss\jboss-5.0.0.<release>\</literal>.
+ Create an environment variable called <literal>JBOSS_HOME</literal> that points to the JBoss Application Server installation directory, for example: <literal>C:\Program Files\JBoss\jboss-<release>\</literal>.
</para>
</listitem>
<listitem>
<para>
- In order to run JBoss Application Server from the command line, add the <literal>jboss-5.0.0.<release>\bin</literal> directory to your path, for example: <literal>C:\Program Files\JBoss\jboss-5.0.0.<release>\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
+ In order to run JBoss Application Server from the command line, add the <literal>jboss-<release>\bin</literal> directory to your path, for example: <literal>C:\Program Files\JBoss\jboss-<release>\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
</para>
</listitem>
</itemizedlist>
- You are now ready to start the JBoss Application Server. For more information on starting or stopping the server, please refer to <ulink url="http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/Getting_Started_Guide/beta500/html-single/index.html#Starting_and_Stopping_the_Server">Getting Started Guide</ulink>.
+ You are now ready to start the JBoss Application Server.
</para>
</section>
@@ -1465,46 +1465,37 @@
<!--Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:-->
</para>
-<programlisting>
-
-[vrenish at vinux bin]$ ./run.sh
-=====================================================
-<!--
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /home/vrenish/jboss-4.2.2
-
- JAVA: /usr/java/jdk1.5.0_11/bin/java
-
- JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.cli ent.gcInterval=3600000
- -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.prefer IPv4Stack=true
-
- CLASSPATH: /home/vrenish/jboss-4.2.2/bin/run.jar:/u sr/java/jdk1.5.0_11/lib/tools.jar
-
-=====================================================
-
-18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)...
+<screen>
+[samson at dhcp-1-150 bin]$ sh run.sh
+=========================================================================
+
+JBoss Bootstrap Environment
+
+JBOSS_HOME: /downloads/jboss-5.0.0.Beta
+
+JAVA: /usr/java/jdk1.5.0_14/bin/java
+
+JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
+
+CLASSPATH: /downloads/jboss-5.0.0.Beta/bin/run.jar:/usr/java/jdk1.5.0_14/lib/tools.jar
+
+=========================================================================
+
+09:52:23,793 INFO [ServerImpl] Starting JBoss (Microcontainer)...
.
+.
.
-.
-.
-.
-18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
-18:45:50,449 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03 ,Sun Microsystems Inc.
-18:45:50,449 INFO [ServerInfo] OS-System: Linux 2.6.9-42.0.3.EL,i386
-18:45:51,824 INFO [Server] Core system initialized
-18:45:59,622 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 /
-18:45:59,659 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml-->
-
-</programlisting>
+09:56:59,231 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
+09:56:59,246 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200803061035)] Started in 4m:35s:367ms
+</screen>
<note>
<para>
- Note that there is no "Server Started" message shown at the console when the server is started using the <literal>default</literal> profile, which is the default profile used when no other is specified. You may run the production This message may be observed in the <filename>server.log</filename> file located in the <filename>server/defaut/log</filename> subdirectory.
+ Note that there is no "Server Started" message shown at the console when the server is started using the <literal>default</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>server/defaut/log</filename> subdirectory.
</para>
</note>
<para>
Now open <literal>http://localhost:8080</literal> in your web browser. (Make sure you dont have anything else already on your machine using that port).<footnote><para>
- Note that on some machines, the name localhost won’t resolve properly and you should use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation"/>.
+ Note that on some machines, the name localhost may not resolve properly and you may need to use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to the following: <xref linkend="Test_your_Installation-Test_your_Installation"/>.
</para>
<para>
<figure id="Test_your_Installation-Test_your_Installation">
@@ -1517,7 +1508,7 @@
</figure>
</para>
<para>
- You are now ready to use the JBoss Application Server. Refer to the Getting Started Guide for more information about the Server layout and example applications showcasing JBoss in action.
+ You are now ready to use the JBoss Application Server.
</para>
</chapter>
<chapter id="The_JBoss_Server___A_Quick_Tour">
@@ -1568,7 +1559,7 @@
<term>all</term>
<listitem>
<para>
- The all configuration starts all the available services. This includes the RMI/IIOP and clustering services, which aren’t loaded in the default configuration.
+ 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>
@@ -1680,7 +1671,7 @@
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-The_default_Server_Configuration_File_Set">
<title>The "default" Server Configuration File Set</title>
<para>
- The "<literal>default</literal>" server configuration file set is located in the <literal><JBoss_Home>/server/default</literal> directory. The following example illustrates a truncated directory structure of the <literal>jboss-as-5.0.0<release></literal> server configuration files:
+ The "<literal>default</literal>" server configuration file set is located in the <literal><JBoss_Home>/server/default</literal> directory. The following example illustrates a truncated directory structure of the <literal>jboss-as-<release></literal> server configuration files:
<screen>[user at localhost <JBoss_Home>]$ tree
|-- bin
|-- client
@@ -1776,7 +1767,7 @@
| |-- log
| | |-- boot.log
| | |-- server.log
-| | `-- server.log.2008-01-09
+| | `-- server.log.2008-08-09
| |-- tmp
| `-- work
| `-- jboss.web
@@ -2376,14 +2367,14 @@
JBoss Bootstrap Environment
- JBOSS_HOME: /home/user/jboss-as-5.0.0/jboss-as
+ JBOSS_HOME: /home/user/jboss-as-version/jboss-as
JAVA: java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.client.
gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
- CLASSPATH: /home/user/jboss-as-5.0.0/jboss-as/bin/run.jar
+ CLASSPATH: /home/user/jboss-as-version/jboss-as/bin/run.jar
=========================================================================
@@ -2616,7 +2607,7 @@
This creates a new file appender and specifies that it should be used by the logger (or category) for the package <literal>org.jboss.ejb.plugins.cmp</literal>.
</para>
<para>
- The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to the name. You will notice that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
+ The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to their filenames. Please note that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
</para>
</section>
@@ -2626,7 +2617,7 @@
The security domain information is stored in the file <filename>conf/login-config.xml</filename> as a list of named security domains, each of which specifies a number of JAAS <footnote><para>
The Java Authentication and Authorization Service. JBoss uses JAAS to provide pluggable authentication modules. You can use the ones that are provided or write your own if you have more specific requirements.
</para>
- </footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application that ship with JBoss.
+ </footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application which ships with JBoss.
</para>
<para>
Almost every aspect of the JBoss server can be controlled through the JMX Console, so it is important to make sure that, at the very least, the application is password protected. Otherwise, any remote user could completely control your server. To protect it, we will add a security domain to cover the application.
@@ -2737,7 +2728,7 @@
</title>
<para>
- The Release Notes for JBoss Application Server 4.0.0 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 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.
</para>
</section>
@@ -2972,8 +2963,8 @@
<para>
<emphasis role="bold">create.xhtml</emphasis>: When you try to create a new task, this JSF page captures the input data. We use the <literal>todoBean</literal> to back the form input text fields. The #{todoBean.todo.title} symbol refers to the "title" property of the "todo" object in the "TodoBean" class. The #{todoBean.todo.description} symbol refers to the "description" property of the "todo" object in the "TodoBean" class. The #{todoBean.persist} symbol refers to the "persist" method in the "TodoBean" class. This method creates the "Todo" instance with the input data (title and description) and persists the data.
</para>
- <para>
-<programlisting>
+
+<programlisting role="xml">
<h:form id="create">
<table>
<tr>
@@ -2997,7 +2988,9 @@
action="#{todoBean.persist}"/>
</h:form>
</programlisting>
- <xref linkend="Sample_JSF_EJB3_Application-JSF_Web_Pages-jsfejb3_create_todo"/> shows the "Create Todo" web page with the input fields mapped to the data model.
+
+<para>
+ <xref linkend="Sample_JSF_EJB3_Application-JSF_Web_Pages-jsfejb3_create_todo"/> shows the "Create Todo" web page with the input fields mapped to the data model.
</para>
<figure id="Sample_JSF_EJB3_Application-JSF_Web_Pages-jsfejb3_create_todo">
<title>The "Create Todo" web page </title>
@@ -3052,8 +3045,8 @@
<para>
<emphasis role="bold">edit.xhtml</emphasis>: This page allows you to edit the "todo" item's 'title' and 'description' properties. The #{todoBean.update} and #{todoBean.delete} symbols represent the "update" and "delete" methods in the "TodoBean" class.
</para>
- <para>
-<programlisting>
+
+<programlisting role="xml">
<h2>Edit #{todoBean.todo.title}</h2>
<h:form id="edit">
<input type="hidden" name="tid" value="#{todoBean.todo.id}"/>
@@ -3081,6 +3074,7 @@
action="#{todoBean.delete}"/>
</h:form>
</programlisting>
+<para>
<xref linkend="Sample_JSF_EJB3_Application-JSF_Web_Pages-jsfejb3_edit_todo"/> shows the "Edit Todo" web page with the mapping to the data model.
</para>
<figure id="Sample_JSF_EJB3_Application-JSF_Web_Pages-jsfejb3_edit_todo">
@@ -3113,7 +3107,8 @@
<emphasis role="bold">Business interface</emphasis>: <literal>TodoDaoInt.java</literal>
</para>
<para>We define here the methods that need to be implemented by the bean implementation class. Basically, the business methods that will be used in our application are defined here.
-<programlisting>
+
+<programlisting role="JAVA">
public interface TodoDaoInt {
public void persist (Todo todo);
@@ -3171,7 +3166,7 @@
<section id="Sample_JSF_EJB3_Application-Configuration_and_Packaging">
<title>Configuration and Packaging</title>
<para>
- We will build the sample application using Ant and explore the configuration and packaging details. If you haven't installed Ant yet, do so now.
+ We will build the sample application using Ant and explore the configuration and packaging details. Please install Ant if currently not installed on your computer.
</para>
<section id="Building_The_Application">
<title>Building The Application</title>
@@ -3185,7 +3180,7 @@
compile:
[mkdir] Created dir: /jboss/gettingstarted/jsfejb3/build/classes
- [javac] Compiling 4 source files to /home/skittoli/Desktop/gettingstarted/jsfejb3/build/classes
+ [javac] Compiling 4 source files to /home/user/Desktop/gettingstarted/jsfejb3/build/classes
[javac] Note: /jboss/gettingstarted/jsfejb3/src/TodoDao.java uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
@@ -3835,10 +3830,10 @@
<chapter id="Using_other_Databases">
<title>Using other Databases</title>
<para>
- In the previous chapters, we’ve just 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 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
</para>
<para>
- Having a database included with JBossAS 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.
+ Having a database included with JBossAS 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.
</para>
<para>
In this chapter we will explain in details how to configure and deploy a datasource to connect JBossAS to the most popular database servers available on the market today.
@@ -3887,23 +3882,20 @@
Then create a text file in the deploy directory called mysql-ds.xml with the following datasource descriptor:
</para>
-<programlisting> <![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<datasources>
- <local-tx-datasource>
- <jndi-name>DefaultDS</jndi-name>
- <connection-url>jdbc:mysql://localhost:3306/test</connection-url>
- <driver-class>com.mysql.jdbc.Driver</driver-class>
- <user-name>root</user-name>
- <password>jboss</password>
- <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
- <metadata>
- <type-mapping>mySQL</type-mapping>
- </metadata>
- </local-tx-datasource>
-</datasources>
-]]>
-</programlisting>
+<programlisting role="XML"><?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/test</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name>root</user-name>
+ <password>jboss</password>
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
+ <metadata>
+ <type-mapping>mySQL</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources></programlisting>
<para>
The datasource is pointing at the database called test provided by default with MySQL 5.x.
@@ -3913,29 +3905,6 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<section id="Using_MySQL_as_the_Default_DataSource-Testing_the_MySQL_DataSource">
<title>Testing the MySQL DataSource</title>
<para>
@@ -3964,25 +3933,24 @@
</para>
<para>
Then create a text file in the <filename>deploy</filename> directory called <filename>oracle-ds.xml</filename> with the following datasource descriptor :
+ </para>
- <programlisting><![CDATA[
- <?xml version="1.0" encoding="UTF-8"?>
- <datasources>
- <local-tx-datasource>
- <jndi-name>DefaultDS</jndi-name>
- <connection-url>jdbc:oracle:thin:@localhost:1521:xe</connection-url>
- <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
- <user-name>SYSTEM</user-name>
- <password>jboss</password>
- <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
- <metadata>
- <type-mapping>Oracle9i</type-mapping>
- </metadata>
- </local-tx-datasource>
- </datasources>
- ]]>
- </programlisting>
-
+<programlisting role="XML"><?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:oracle:thin:@localhost:1521:xe</connection-url>
+ <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
+ <user-name>SYSTEM</user-name>
+ <password>jboss</password>
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
+ <metadata>
+ <type-mapping>Oracle9i</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources></programlisting>
+
+ <para>
The datasource is pointing at the database/SID called “xe” provided by default with Oracle XE.
</para>
<para>
@@ -4193,10 +4161,10 @@
<title>Further Information Sources</title>
<para>
- For a longer introduction to JBoss, see <emphasis>JBoss: A Developer's Notebook</emphasis>. (O'Reilly, 2005. Norman Richards, Sam Griffith).
+ Developers wanting to get familiar with software development and implementation in JBoss Application Server can read: <emphasis>JBoss: A Developer's Notebook</emphasis>. (O'Reilly, 2005. Norman Richards, Sam Griffith).
</para>
<para>
- For more comprehensive JBoss documentation covering advanced JBoss topics, refer to the manuals available online at <ulink url="http://www.redhat.com/docs/manuals/jboss"/>.
+ For more comprehensive JBoss documentation covering advanced JBoss topics, refer to the manuals available online at <ulink url="http://www.jboss.org/jbossas/docs"/>.
</para>
<para>
For general EJB instruction, with thorough JBoss coverage, see <emphasis> Enterprise JavaBeans, 4th Edition</emphasis>. (O'Reilly, 2004. Richard Monson-Haeful, Bill Burke, Sacha Labourey)
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml 2008-10-01 01:53:53 UTC (rev 78974)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml 2008-10-01 02:03:46 UTC (rev 78975)
@@ -47,23 +47,24 @@
<!--put back css -->
<formats>
- <format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>Installation_And_Getting_Started_Guide.pdf</finalName>
- </format>
<format>
<formatName>html</formatName>
<stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
-
- <format>
+ <format>
<formatName>html_single</formatName>
<stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
+ <format>
+ <formatName>pdf</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <finalName>Installation_And_Getting_Started_Guide.pdf</finalName>
+ </format>
+
+
<!--<format>
<formatName>eclipse</formatName>
<stylesheetResource>classpath:/xslt/main-eclipse.xsl</stylesheetResource>
More information about the jboss-cvs-commits
mailing list