Author: sabrashevich Date: 2007-08-20 10:07:09 -0400 (Mon, 20 Aug 2007) New Revision: 3231 Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GetStartSeamGen.xml trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GettingStartedWithRHDS.xml trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml Log: http://jira.jboss.com/jira/browse/EXIN-373 text highlighted Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GetStartSeamGen.xml =================================================================== --- trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GetStartSeamGen.xml 2007-08-17 21:40:15 UTC (rev 3230) +++ trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GetStartSeamGen.xml 2007-08-20 14:07:09 UTC (rev 3231) @@ -13,14 +13,14 @@ <para>The Red Hat Developer Studio provides sophisticated tools for enterprise applications. With the Red Hat Developer Studio, you can get started very quickly with a web prototype, and then scale up your application to include enterprise features (e.g., business processes, web services, etc.) using the same developer tools. It is a &quot;scalable&quot; RAD (Rapid Application Development) tool.</para> - <para>A core element that makes the Red Hat Developer Studio &quot;scalable&quot; is the JBoss Seam framework. Seam is a fully featured application framework on top of Java EE 5. It is also one of the most popular enterprise Java framework today. Seam deeply integrates many other standard-based or open source frameworks (e.g., JSF, EJB3, JMS, Web Services, jBPM, JBoss Rules, Ajax4jsf, RichFaces, Facelets, Spring, iText, Quartz, TestNG etc.), and provides a single programming model for developers to &quot;drive&quot; those underlying frameworks via simple annotated POJOs (Plain Old Java Objects). It makes life easier for developers to tackle complex enterprise applications with many component frameworks.</para> + <para>A core element that makes the Red Hat Developer Studio &quot;scalable&quot; is the JBoss <property>Seam</property> framework. <property>Seam</property> is a fully featured application framework on top of Java EE 5. It is also one of the most popular enterprise Java framework today. <property>Seam</property> deeply integrates many other standard-based or open source frameworks (e.g., JSF, EJB3, JMS, Web Services, jBPM, JBoss Rules, Ajax4jsf, RichFaces, Facelets, Spring, iText, Quartz, TestNG etc.), and provides a single programming model for developers to &quot;drive&quot; those underlying frameworks via simple annotated POJOs (Plain Old Java Objects). It makes life easier for developers to tackle complex enterprise applications with many component frameworks.</para> - <para>In this chapter, we will cover how to build a simple Seam web application in minutes with the Red Hat Developer Studio.</para> + <para>In this chapter, we will cover how to build a simple <property>Seam</property> web application in minutes with the Red Hat Developer Studio.</para> <section> <title>Create a Seam Project</title> - <para>To create a new web application in Seam, select <emphasis role="italic">New > Project ... > Seam > Seam Web Project</emphasis>. You will be prompted to enter a name and a location directory for your new project. You will also be asked to choose a JBoss AS server to deploy the project. You must choose the JBoss AS 4.2.0 instance we had defined in the JBoss AS Server manager view.</para> + <para>To create a new web application in <property>Seam</property>, select <emphasis>New &gt; Project ... &gt; Seam &gt; Seam Web Project</emphasis>. You will be prompted to enter a name and a location directory for your new project. You will also be asked to choose a JBoss AS server to deploy the project. You must choose the JBoss AS 4.2.0 instance we had defined in the JBoss AS Server manager view.</para> <figure> <title>Create a Seam project</title> @@ -31,7 +31,7 @@ </mediaobject> </figure> - <para>Next, you will be asked to select the &quot;features&quot; you want to use in your project. This allows Red Hat Developer Studio to setup the appropriate tooling for your project. Since JBoss Seam integrates all popular Java EE frameworks, you can select any combination of technologies from the list. Here, for this project, we will select Dynamic Web Module, Java, Java Persistence (JPA), JavaServer Faces (JSF), and Seam Facet for a typical database-driven web application.</para> + <para>Next, you will be asked to select the &quot;features&quot; you want to use in your project. This allows Red Hat Developer Studio to setup the appropriate tooling for your project. Since JBoss <property>Seam</property> integrates all popular Java EE frameworks, you can select any combination of technologies from the list. Here, for this project, we will select Dynamic Web Module, Java, Java Persistence (JPA), JavaServer Faces (JSF), and <property>Seam</property> Facet for a typical database-driven web application.</para> <figure> <title>Select toolings for the project</title> @@ -93,7 +93,7 @@ <orderedlist continuation="continues"> <listitem><para>In the next dialog select Add button.</para></listitem> - <listitem><para>Select Hypersonic database: <emphasis role="italic">Hypersonic &gt; 1.8 &gt; Hypersonic DB</emphasis></para></listitem> + <listitem><para>Select Hypersonic database: <emphasis>Hypersonic &gt; 1.8 &gt; Hypersonic DB</emphasis></para></listitem> </orderedlist> <figure> @@ -117,7 +117,7 @@ <orderedlist continuation="continues"> <listitem><para>Select hsqldb.jar in Driver File panel and click the button Remove jar/Zip.</para></listitem> <listitem><para>Select Add jar/Zip.</para></listitem> - <listitem><para>Select hsqldb driver which is located in <emphasis role="italic">jboss-eap &gt; jboss-as &gt; server &gt; default &gt; lib</emphasis> folder of RHDS installation.</para></listitem> + <listitem><para>Select hsqldb driver which is located in <emphasis>jboss-eap &gt; jboss-as &gt; server &gt; default &gt; lib</emphasis> folder of RHDS installation.</para></listitem> </orderedlist> <figure> <title>Adding driver</title> @@ -168,7 +168,7 @@ </mediaobject> </figure> - <para>The project setup wizard also asks you to configure how Seam generates code for the project. The Seam Home Folder should point to a valid Seam distribution. By default, it is set to the Seam distribution bundled in your Red Hat Developer Studio tool. For the deployment format, choose WAR deployment if you want to use POJOs for UI event handling and business logic; choose EAR deployment if you want to EJB3 beans for added features. In most web applications, the WAR deployment option would suffice. You should also enter Java packages for the entity beans (for database mapping) and session beans (for action handlers). All generated code will be placed in those packages. </para> + <para>The project setup wizard also asks you to configure how <property>Seam</property> generates code for the project. The <property>Seam</property> Home Folder should point to a valid <property>Seam</property> distribution. By default, it is set to the <property>Seam</property> distribution bundled in your Red Hat Developer Studio tool. For the deployment format, choose WAR deployment if you want to use POJOs for UI event handling and business logic; choose EAR deployment if you want to EJB3 beans for added features. In most web applications, the WAR deployment option would suffice. You should also enter Java packages for the entity beans (for database mapping) and session beans (for action handlers). All generated code will be placed in those packages. </para> <figure> <title>Enter Java packages for generated code</title> @@ -206,7 +206,7 @@ </mediaobject> </figure> - <para>To make simple changes to the page, you just need to double click on the <emphasis role="italic">WebContent/home.xhtml file</emphasis> and edit it in the visual editor. Notice that the visual editor lets you both the XHTML code and the rendered page. The rendered view is designed to make it easy to find stuff in a complex XHTML page.</para> + <para>To make simple changes to the page, you just need to double click on the <emphasis>WebContent/home.xhtml file</emphasis> and edit it in the visual editor. Notice that the visual editor lets you both the XHTML code and the rendered page. The rendered view is designed to make it easy to find stuff in a complex XHTML page.</para> <figure> <title>Making changes in the visual editor</title> @@ -217,7 +217,7 @@ </mediaobject> </figure> - <para>Once you finished editing, save the file (<emphasis role="italic">File &gt; Save</emphasis>), re-deploy the application, and reload the browser to see the changes.</para> + <para>Once you finished editing, save the file (<emphasis>File &gt; Save</emphasis>), re-deploy the application, and reload the browser to see the changes.</para> <figure> <title>The front page is changed</title> @@ -237,7 +237,7 @@ <section> <title>Add a Web Page and an Action</title> - <para>To add a new page and related UI action to the project, use the <emphasis role="italic">New &gt; Other ... &gt; Seam &gt; Seam Form</emphasis> wizard. You are prompted to enter the name of the web page, the name for the Seam component that handles UI actions from the page, and UI action method name.</para> + <para>To add a new page and related UI action to the project, use the <emphasis>New &gt; Other ... &gt; Seam &gt; Seam Form</emphasis> wizard. You are prompted to enter the name of the web page, the name for the <property>Seam</property> component that handles UI actions from the page, and UI action method name.</para> <figure> <title>New form for the application</title> @@ -292,7 +292,7 @@ </ui:composition> ]]></programlisting> - <para>The #{simpleAction.value} notation on the web page maps to the &quot;value&quot; property in the backend component named &quot;simpleAction&quot;, and the #{simpleAction.hello} notation indicates that the hello() method is called when the button is clicked on. Here is the &quot;simpleAction&quot; named backend Seam component generated by the wizard.</para> + <para>The #{simpleAction.value} notation on the web page maps to the &quot;value&quot; property in the backend component named &quot;simpleAction&quot;, and the #{simpleAction.hello} notation indicates that the hello() method is called when the button is clicked on. Here is the &quot;simpleAction&quot; named backend <property>Seam</property> component generated by the wizard.</para> <programlisting role="JAVA"><![CDATA[ @Name("simpleAction") @@ -348,7 +348,7 @@ </mediaobject> </figure> - <para>Seam supports many different input validation annotations. To see an example, you can replace the @Length(max=10) annotation with the following. It would require the input string to have a first name and last name separated by a space. If the validation fails, the web page would print the customized error message.</para> + <para><property>Seam</property> supports many different input validation annotations. To see an example, you can replace the @Length(max=10) annotation with the following. It would require the input string to have a first name and last name separated by a space. If the validation fails, the web page would print the customized error message.</para> <programlisting role="JAVA"><![CDATA[ @NotNull @@ -428,7 +428,7 @@ <section> <title>Add Security to the Application</title> - <para>You have probably noticed that the web page template has a login link at the top of the page. You can use the Seam security framework to secure access to any web page or web action. You can implement the login logic in the XXXX method. In the following example, we just use hardcoded username and password. But you can easily change it to use database, LDAP or any other means.</para> + <para>You have probably noticed that the web page template has a login link at the top of the page. You can use the <property>Seam</property> security framework to secure access to any web page or web action. You can implement the login logic in the XXXX method. In the following example, we just use hardcoded username and password. But you can easily change it to use database, LDAP or any other means.</para> <programlisting role="JAVA"><![CDATA[ ]]></programlisting> Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GettingStartedWithRHDS.xml =================================================================== --- trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GettingStartedWithRHDS.xml 2007-08-17 21:40:15 UTC (rev 3230) +++ trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/GettingStartedWithRHDS.xml 2007-08-20 14:07:09 UTC (rev 3231) @@ -28,7 +28,7 @@ In that case you can skip the next step mentioned here. But it is recommended to use the SysV service scripts for production servers.</para></listitem> <listitem><para>Download and install the appropriate -compat RPM from JPackage <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-f...;. Please ensure you choose a matching version of the -compat package to the JDK you installed.</para></listitem> - <listitem><para>Create an environment variable that points to the JDK installation directory and call it JAVA_HOME. Add <emphasis role="italic">$JAVA_HOME/bin</emphasis> to the system path to be able to run java from the + <listitem><para>Create an environment variable that points to the JDK installation directory and call it JAVA_HOME. Add <emphasis>$JAVA_HOME/bin</emphasis> to the system path to be able to run java from the command line. You can do this by adding the following lines to the .bashrc file in your home directory.</para></listitem> </itemizedlist> <programlisting><![CDATA[#In this example /usr/java/jdk1.5.0_11 is the JDK installation directory. @@ -100,7 +100,7 @@ <listitem><para>Create an environment variable called JAVA_HOME that points to the JDK installation directory, for example:</para></listitem> </itemizedlist> <programlisting><![CDATA[C:\Program Files\Java\jdk1.5.0_11\]]></programlisting> - <para>In order to run java from the command line add the <emphasis role="italic">jre\bin</emphasis> directory to your path, for example:</para> + <para>In order to run java from the command line add the <emphasis>jre\bin</emphasis> directory to your path, for example:</para> <programlisting><![CDATA[C:\Program Files\Java\jdk1.5.0_11\jre\bin]]></programlisting> <para>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> @@ -231,27 +231,26 @@ <para><emphasis role="bold">Do I need to have JBoss server installed to run Red Hat Developer Studio?</emphasis></para> <para>No. Red Hat Developer Studio already comes bundled with JBoss server. We bundle it together so that you don&apos;t need to download any additional software and can test your application in a Web browser right away.</para> - <para>If you want to use a different JBoss server installation, after Red Hat Developer Studio is installed open Servers View (select <emphasis role="italic">Window &gt; Show View &gt; Others &gt; Server &gt; Servers</emphasis>), then right click on this <emphasis role="italic">view &gt; New &gt; Server</emphasis> and follow the wizards steps to point to another Jboss server installation.</para> + <para>If you want to use a different JBoss server installation, after Red Hat Developer Studio is installed open Servers View (select <emphasis>Window &gt; Show View &gt; Others &gt; Server &gt; Servers</emphasis>), then right click on this <emphasis>view &gt; New &gt; Server</emphasis> and follow the wizards steps to point to another Jboss server installation.</para> <para>Red Hat Developer Studio works with any servlet container, not just JBoss. For more information on deployment, please see the Deploying Your Application section.</para> </section> <section id="Importing_Projects"> <title>Importing Projects</title> <para><emphasis role="bold">I have an existing Struts or JSF project. Can I open the project in RHDS?</emphasis></para> - <para>Yes. From main menu select <emphasis role="italic">File &gt; Import &gt; Other &gt; JSF Project (or Struts Project)</emphasis> and follow wizards steps.</para> + <para>Yes. From main menu select <emphasis>File &gt; Import &gt; Other &gt; JSF Project (or Struts Project)</emphasis> and follow wizards steps.</para> <para><emphasis role="bold">Can I import a .war file?</emphasis></para> - <para>Yes. Select <emphasis role="italic">File &gt; Import &gt; Web &gt; WAR file</emphasis> Then follow importing steps.</para> + <para>Yes. Select <emphasis>File &gt; Import &gt; Web &gt; WAR file</emphasis>, then follow importing steps.</para> </section> <section id="Troubleshooting"> <title>Troubleshooting, Problems, Configuration, Error Messages</title> <para><emphasis role="bold">Is it possible to increase the performance of Eclipse after installing your product? My Eclipse now crawls.</emphasis></para> - <para>Red Hat Developer Studio preconfigures eclipse via the eclipse.ini file to allocate extra memory, but if you for some reason are using your own version of Eclipse then - by default, Eclipse allocates only 128 Mb of memory whatever physical memory you actually have installed. You can significantly increase performance if you allocate more memory. For example:</para> + <para>Red Hat Developer Studio preconfigures eclipse via the eclipse.ini file to allocate extra memory, but if you for some reason need more memory then by default, you can manually make adjustments in this file. For example:</para> <para>-vmargs -Xms128m -Xmx512m -XX:MaxPermSize=128m</para> <para><emphasis role="bold">How can I add my own tag library to the Red Hat Palette?</emphasis></para> - <para>See <ulink url="http://labs.jboss.com/jbossjsftools/docs">Adding Tag Libraries</ulink> in JBossJSFTools Guide.</para> + <para>See <ulink url="http://www.redhat.com/developers/rhds/JSFTools/JavaServerFacesS... Tag Libraries</ulink> in JBossJSFTools Guide.</para> <para><emphasis role="bold">I see the Oracle ADF Faces component library tags in the Red Hat Palette, but I can&apos;t seem to find the libraries for ADF. How do I use this component library with RHDS?</emphasis></para> - <para>See <ulink url="http://labs.jboss.com/jbossrhdsuserguide/docs">Adding Support for the Oracle ADF Components Library</ulink> in the RHDS User Guide.</para> + <para>See <ulink url="http://www.redhat.com/developers/rhds/JSFTools/JavaServerFacesS... Support for the Oracle ADF Components Library</ulink> in the RHDS User Guide.</para> </section> </section> Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml =================================================================== --- trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml 2007-08-17 21:40:15 UTC (rev 3230) +++ trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml 2007-08-20 14:07:09 UTC (rev 3231) @@ -11,7 +11,7 @@ </keywordset> </chapterinfo> <title>Manage JBoss AS from Red Hat Developer Studio</title> - <para>Red Hat Developer Studio ships with JBoss EAP v.4.2 bundled. When you followed the default installation of Red Hat Developer Studio, you already have a JBoss 4.2 server installed and defined. To run JBoss AS 4.2 you need JDK 1.5. JDK 6 is not formally supported yet, although you may be able to start the server with it.</para> + <para>Red Hat Developer Studio ships with <property>JBoss EAP v.4.2</property> bundled. When you followed the default installation of Red Hat Developer Studio, you already have a <property>JBoss 4.2 server</property> installed and defined. To run <property>JBoss AS 4.2</property> you need JDK 1.5. JDK 6 is not formally supported yet, although you may be able to start the server with it.</para> <section id="JBossbundled"> <?dbhtml filename="JBossbundled.html"?> <title>How to manage the JBoss AS bundled in RHDS</title> @@ -19,9 +19,9 @@ <section id="StartingServer"> <?dbhtml filename="StartingServer.html"?> <title>Starting JBoss server</title> - <para>Starting JBoss server is quite simple. Red Hat Developer Studio allows you control its behaviour through a special toolbar: start it in a regular or debug mode, stop it, or restart it.</para> + <para>Starting <property>JBoss server</property> is quite simple. Red Hat Developer Studio allows you control its behaviour through a special toolbar: start it in a regular or debug mode, stop it, or restart it.</para> <orderedlist> - <listitem><para>To launch the server click the green-with-white-arrow icon on the JBoss Server View or right click server name in this view and select &quot;Start&quot;. If this view is not open select <emphasis role="italic">Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View</emphasis></para></listitem> + <listitem><para>To launch the server click the green-with-white-arrow icon on the <property>JBoss Server</property> View or right click server name in this view and select &quot;Start&quot;. If this view is not open select <emphasis>Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View</emphasis></para></listitem> </orderedlist> <figure> <title>Starting from icon</title> @@ -51,7 +51,7 @@ </imageobject> </mediaobject> </figure> -<para>When server has started you should see &quot;Started&quot; right to its name in JBoss Server view (column &quot;Status&quot;).</para> +<para>When server has started you should see &quot;Started&quot; right to its name in <property>JBoss Server</property> view (column &quot;Status&quot;).</para> <figure> <title>Server is started</title> <mediaobject> @@ -60,7 +60,7 @@ </imageobject> </mediaobject> </figure> -<para>To see event log after the server is started expand &quot;Event Log&quot; branch beneath JBoss Servers View:</para> +<para>To see event log after the server is started expand &quot;Event Log&quot; branch beneath <property>JBoss Server</property> View:</para> <figure> <title>Event Log</title> <mediaobject> @@ -73,7 +73,7 @@ <section id="StoppingJBoss"> <?dbhtml filename="StoppingJBoss.html"?> <title>Stopping JBoss server</title> - <para>To stop the server click the Stop icon in JBoss Server View or right click the server name and press Stop.</para> + <para>To stop the server click the Stop icon in <property>JBoss Server</property> View or right click the server name and press Stop.</para> <figure> <title>Stopping server</title> <mediaobject> @@ -87,7 +87,7 @@ <section id="ServerPreferences"> <?dbhtml filename="ServerPreferences.html"?> <title>Server Container Preferences</title> - <para>You can control how Red Hat Developer Studio interacts with servlet containers in Preferences. Select <emphasis role="italic">Window &gt; Preferences &gt; JBoss Tools &gt; JBoss Servers</emphasis> and switch to the desired server:</para> + <para>You can control how Red Hat Developer Studio interacts with servlet containers in Preferences. Select <emphasis>Window &gt; Preferences &gt; JBoss Tools &gt; JBoss Servers</emphasis> and switch to the desired server:</para> <figure> <title>Server preferences</title> <mediaobject> @@ -96,7 +96,7 @@ </imageobject> </mediaobject> </figure> -<para>Also you can double click the server name in JBoss Server view and open an Overview of the server. Here you can specify some common settings: host name, server name, runtime and so on.</para> +<para>Also you can double click the server name in <property>JBoss Server</property> view and open an Overview of the server. Here you can specify some common settings: host name, server name, runtime and so on.</para> <figure> <title>Server overview</title> <mediaobject> @@ -112,15 +112,15 @@ <section id="JBossInstances"> <?dbhtml filename="JBossInstances.html"?> <title>How to manage JBoss AS instances in RHDS</title> - <para>Although Red Hat Developer Studio works closely with JBoss EAP 4.2 we do not ultimately tie you to any particular server for deployment. There are some servers that Studio supports directly (through the bundled Eclipse WTP plug-ins). Suppose you want to deploy the application to JBoss 4.2.1 server. First of all you need to install it.</para> + <para>Although Red Hat Developer Studio works closely with <property>JBoss EAP 4.2</property> we do not ultimately tie you to any particular server for deployment. There are some servers that Studio supports directly (through the bundled Eclipse WTP plug-ins). Suppose you want to deploy the application to <property>JBoss 4.2.1 server</property>. First of all you need to install it.</para> <section id="JBossInstalling"> <?dbhtml filename="JBossInstalling.html"?> <title>JBoss AS Installation</title> <orderedlist> -<listitem><para>Download the binary package of JBoss 4.2.1 and save it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads">http://labs.jb... +<listitem><para>Download the binary package of <property>JBoss 4.2.1</property> and save it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads">http://labs.jb... </orderedlist> -<para>It does not matter where on your system you install JBoss. Note, however, that installing JBoss into a directory that has a name containing spaces causes problems in some situations with Sun-based VMs. So try to avoid using installation folders that have spaces in their names.</para> -<para>There is no requirement for root access to run JBoss on UNIX/Linux systems because none of the default ports are within the 0-1023 privileged port range.</para> +<para>It does not matter where on your system you install <property>JBoss</property>. Note, however, that installing <property>JBoss</property> into a directory that has a name containing spaces causes problems in some situations with Sun-based VMs. So try to avoid using installation folders that have spaces in their names.</para> +<para>There is no requirement for root access to run <property>JBoss</property> on UNIX/Linux systems because none of the default ports are within the 0-1023 privileged port range.</para> <orderedlist continuation="continues"> <listitem><para>After you have the binary archive you want to install, use the JDK jar tool (or any other ZIP extraction tool) to extract the jboss-4.2.1.zip archive contents into a location of your choice. The jboss-4.2.1.tgz archive is a gzipped tar file that requires a gnutar compatible tar which can handle the long pathnames in the archive. The extraction process will create a jboss-4.2.1 directory. </para></listitem> </orderedlist> @@ -131,9 +131,9 @@ <title>Adding and configuring JBoss server</title> <para>Now we should add just installed server into server manager in Red Hat Developer Studio.</para> <orderedlist> - <listitem><para>Open the JBoss Server View by selecting <emphasis role="italic">Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View</emphasis>. You will see JBoss Server view.</para></listitem> + <listitem><para>Open the <property>JBoss Server</property> View by selecting <emphasis>Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View</emphasis>. You will see <property>JBoss Server</property> view.</para></listitem> <listitem><para>Right click anywhere in this view and select New Server.</para></listitem> -<listitem><para>Select <emphasis role="italic">JBoss, a division of Red Hat &gt; JBoss v4.2</emphasis> and click the &quot;Installed Runtimes&quot; button to select a new installed runtime.</para></listitem> +<listitem><para>Select <emphasis>JBoss, a division of Red Hat &gt; JBoss v4.2</emphasis> and click the &quot;Installed Runtimes&quot; button to select a new installed runtime.</para></listitem> </orderedlist> <figure> <title>Selecting server type</title> @@ -146,7 +146,7 @@ <orderedlist continuation="continues"> <listitem><para>Click &quot;Add&quot; button to add a new jboss runtime.</para></listitem> - <listitem><para>Select <emphasis role="italic">JBoss, a division of Red Hat &gt; JBoss v4.2</emphasis> and press Next.</para></listitem> + <listitem><para>Select <emphasis>JBoss, a division of Red Hat &gt; JBoss v4.2</emphasis> and press Next.</para></listitem> </orderedlist> <figure> @@ -186,7 +186,7 @@ </imageobject> </mediaobject> </figure> - <para>A new runtime will now appear in the <emphasis role="italic">Preferences &gt; Server &gt; Installed Runtimes</emphasis> dialog.</para> + <para>A new runtime will now appear in the <emphasis>Preferences &gt; Server &gt; Installed Runtimes</emphasis> dialog.</para> <figure> <title>Runtime is added</title> <mediaobject> @@ -218,7 +218,7 @@ </imageobject> </mediaobject> </figure> -<para>A new JBoss server should now appear in JBoss Server View.</para> +<para>A new <property>JBoss server</property> should now appear in <property>JBoss Server</property> View.</para> <figure> <title>New JBoss Server</title> <mediaobject>