[jboss-cvs] JBossAS SVN: r100730 - in projects/docs/enterprise/5.0.1: Installation_Guide/en-US and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 8 22:33:01 EST 2010
Author: laubai
Date: 2010-02-08 22:33:00 -0500 (Mon, 08 Feb 2010)
New Revision: 100730
Modified:
projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml
projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Installation_Alternatives.xml
projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Migration.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Configuration.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Excel.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gettingstarted.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gwt.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Hsearch.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/I18n.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Itext.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Mail.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Preface.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Security.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Testing.xml
projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
Added remaining JIRA corrections for 5.0.1.
Modified: projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -226,20 +226,20 @@
<property>jboss.vfs.forceCopy</property>
</para>
<para>
- This defines how nested jars should be handled. If forceCopy is true (the default), we create a temporary copy of the nested jar, and re-wire VFS accordingly. If forceCopy is false, we handle nested jars in-memory, which doesn't create temporary copy, but is more memory consuming.
+ Defines how nested JARs are handled. If true (the default), a temporary copy of the nested JAR is created and the VFS is re-wired accordingly. If false, nested JARs are handled in-memory. No temporary copy is created, but this option consumes more memory.
</para>
<!--<para>
If the <property>useCopyJarHandler</property> property is used as part of URI query, you can configure force-copy at runtime, per URI root (if it doesn't already exist).
</para>-->
</listitem>
- <listitem>
+ <!--<listitem>
<para>
<property>jboss.vfs.forceVfsJar</property> has the options true and false, with the default being false.
</para>
<para>
By setting this property to true, you can implement the old JAR handling. Set to false by default, old JAR handling was deprecated in favor of new ZIP handling code.
</para>
- </listitem>
+ </listitem>-->
<listitem>
<para>
<property>jboss.vfs.forceNoReaper</property> has the options true and false, with the default being false.
Modified: projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Installation_Alternatives.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Installation_Alternatives.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Installation_Alternatives.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -37,7 +37,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 zip archive. <!--rpm archive-->
</para>
<para>
- Six types of server profiles will be included in your installation - <emphasis>all</emphasis>, <emphasis>default</emphasis>, <emphasis>minimal</emphasis>, <emphasis>production</emphasis>, <emphasis>standard</emphasis>, and <emphasis>web</emphasis>. The Getting Started Guide explains in detail the different server profile sets.
+ Six types of server profiles will be included in your installation - <emphasis>all</emphasis>, <emphasis>default</emphasis>, <emphasis>minimal</emphasis>, <emphasis>production</emphasis>, <emphasis>standard</emphasis>, and <emphasis>web</emphasis>. The different server profile sets are described in further detail in the <citetitle>Administration and Configuration Guide</citetitle> associated with this distribution of Enterprise Application Platform.
</para>
</chapter>
Modified: projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Migration.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Installation_Guide/en-US/Migration.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -100,7 +100,7 @@
</para>
<para>
- For the complete technology matrix and information on the revision level of included components please refer to <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>.
+ For the complete technology matrix and information on the revision level of included components please refer to <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0.cp01/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0.cp01/html-single/Release_Notes/index.html</ulink>.
</para>
</section>
</section>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Configuration.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Configuration.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -956,16 +956,15 @@
<section>
<title>Running Seam in a Portlet</title>
+ <warning>
+ <title>JBoss Portlet Bridge integration is a Technology Preview</title>
+ <para>Technology Preview features are not fully supported under Red Hat subscription level agreements (SLAs), may not be functionally complete, and are not intended for production use. However, these features provide early access to upcoming product innovations, enabling customers to test functionality and provide feedback during the development process. As Red Hat considers making future iterations of Technology Preview features generally available, we will provide commercially reasonable efforts to resolve any reported issues that customers experience when using these features.</para>
+ </warning>
+
<para>
You can use the JBoss Portlet Bridge to run your Seam application in a portlet. The bridge supports JSF within a portlet, and includes extensions for Seam and RichFaces. See <ulink url="http://labs.jboss.com/portletbridge">http://labs.jboss.com/ portletbridge</ulink> for more information.
</para>
- <note>
- <title>Note</title>
- <para>
- Seam Integration with JBoss Portlet Bridge is designated as a technology preview so standard support is not guaranteed.
- </para>
- </note>
</section>
<section>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Excel.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Excel.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Excel.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -2030,7 +2030,7 @@
Output appearance is controlled with a combination of CSS style and tag attributes. CSS style attributes flow from parent to child, and let you use one tag to apply all attributes defined for that tag in the <literal>styleClass</literal> and <literal>style</literal> sheets. <!-- #modify: These paragraphs made very little sense to me. Please review rewritten paragraphs for technical accuracy. "Controlling how the output look is done with a combination of CSSish style attributes and tag attributes. The most common ones (fonts, borders, backgrounds etc) are CSS and some more general settings are in tag attributes. The CSS attributes cascade down from parent to children and within one tag cascades over the CSS classes referenced in the <literal>styleClass</literal> attributes and finally over the CSS attributes defined in the <literal>style</literal> attribute. You can place them pretty much anywhere but e.g. placing a column width setting in a cell nested within that column!
makes little sense." -->
</para>
<para>
- If you have format masks or fonts that use special characters, such as spaces and semicolons, you can escape the css string with <literal>''</literal> characters such as <literal>xls-format-mask:'$;$'</literal>.
+ If you have format masks or fonts that use special characters, such as spaces and semicolons, you can escape the CSS string with <literal>''</literal> characters such as <literal>xls-format-mask:'$;$'</literal>.
</para>
<section id="excel.fontsandlayout.link">
<title>Stylesheet links</title>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -13,7 +13,7 @@
<section>
<title>Before you start</title>
<para>
- Make sure you have JDK 5, JBoss EAP 5, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting.
+ Make sure you have JDK 5, JBoss Enterprise Application Platform 5, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting.
</para>
<para>
Please see the official <ulink url="http://www.jboss.org/tools/download/installation">JBoss Tools installation</ulink> page for the quickest way to get JBoss Tools set up in Eclipse. You can also check out the <ulink url="http://www.jboss.org/community/wiki/InstallingJBossTools">Installing JBoss Tools</ulink> page on the JBoss community wiki for more details and a set of alternative installation approaches.
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gettingstarted.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gettingstarted.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gettingstarted.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -8,7 +8,7 @@
Seam includes a command line utility that makes it easy to set up an Eclipse project, generate some simple Seam skeleton code, and reverse-engineer an application from a preexisting database. This is an easy way to familiarize yourself with Seam.
</para>
<para>
- In this release, <application>seam-gen</application> works best in conjunction with JBoss EAP.
+ In this release, <application>seam-gen</application> works best in conjunction with JBoss Enterprise Application Platform.
</para>
<para>
seam-gen can be used without Eclipse, but this tutorial focuses on using seam-gen with Eclipse for debugging and integration testing. If you would prefer not to use Eclipse, you can still follow this tutorial — all steps can be performed from the command line.
@@ -16,7 +16,7 @@
<section>
<title>Before you start</title>
<para>
- Make sure you have JDK 5 or JDK 6 (see <xref linkend="jdk_dependencies" /> for details), JBoss EAP 5 and Ant 1.7.0, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before you begin this tutorial. Add your JBoss installation to the JBoss Server View in Eclipse. Then, start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution.
+ Make sure you have JDK 5 or JDK 6 (see <xref linkend="jdk_dependencies" /> for details), JBoss Enterprise Application Platform 5 and Ant 1.7.0, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before you begin this tutorial. Add your JBoss installation to the JBoss Server View in Eclipse. Then, start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution.
</para>
<para>
JBoss has sophisticated support for hot redeployment of <filename>WAR</filename>s and <filename>EAR</filename>s. Unfortunately, due to bugs in JVM, repeat redeployment of an EAR (common during development) uses all of the JVM's perm gen space. Therefore, we recommend running JBoss in a JVM with a large perm gen space during development. If you are running JBoss from JBoss IDE, you can configure this in the server launch configuration, under "VM arguments". We suggest the following values:
@@ -41,8 +41,7 @@
First, configure seam-gen for your environment. Just type the following in your command line interface:
</para>
-<programlisting>cd jboss-seam-2.0.x seam setup
-</programlisting>
+<programlisting>cd <seam_distribution_dir> seam setup</programlisting>
<para>
You will receive the following prompt for the required information:
</para>
@@ -118,7 +117,7 @@
<programlisting>seam new-project
</programlisting>
-<programlisting>C:\Projects\jboss-seam>seam new-project
+<programlisting><seam_distribution_dir> seam new-project
Buildfile: build.xml
...
new-project:
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gwt.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gwt.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Gwt.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -4,6 +4,11 @@
<chapter id="gwt" >
<title>Seam and the Google Web Toolkit</title>
+ <warning>
+ <title>Google Web Toolkit integration is a Technology Preview</title>
+ <para>Technology Preview features are not fully supported under Red Hat subscription level agreements (SLAs), may not be functionally complete, and are not intended for production use. However, these features provide early access to upcoming product innovations, enabling customers to test functionality and provide feedback during the development process. As Red Hat considers making future iterations of Technology Preview features generally available, we will provide commercially reasonable efforts to resolve any reported issues that customers experience when using these features.</para>
+ </warning>
+
<para>
If you prefer to develop dynamic AJAX (Asynchronous Java and XML) applications with the Google Web Toolkit (GWT), Seam provides an integration layer that allows GWT widgets to interact directly with Seam components.
</para>
@@ -11,10 +16,6 @@
In this section, we assume you are already familiar with GWT Tools, and focus only on the Seam integration. You can find more information at <ulink url="http://code.google.com/webtoolkit/">http://code.google.com/webtoolkit/ </ulink>.
</para>
- <note>
- <title>Note</title>
- <para>GWT integration in Seam is designated as a technology preview so standard support is not guaranteed.</para>
- </note>
<section>
<title>Configuration</title>
<para>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Hsearch.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Hsearch.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Hsearch.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -39,7 +39,7 @@
</properties>
</persistence-unit>]]>
</programlisting>
- <para>
+ <!--<para>
To target Hibernate Annotations or EntityManager 3.2.x (embedded into JBoss AS 4.2.x and later), you must also configure the appropriate event listeners.
</para>
@@ -47,10 +47,10 @@
<jta-data-source>java:/DefaultDS</jta-data-source>
<properties>
[...]
- <!-- use a file system based index -->
+ # use a file system based index
<property name="hibernate.search.default.directory_provider"
value="org.hibernate.search.store.FSDirectoryProvider"/>
- <!-- directory where the indexes will be stored -->
+ # directory where the indexes will be stored
<property name="hibernate.search.default.indexBase"
value="/Users/prod/apps/dvdstore/dvdindexes"/>
<property name="hibernate.ejb.event.post-insert"
@@ -61,11 +61,11 @@
value="org.hibernate.search.event.FullTextIndexEventListener"/>
</properties>
</persistence-unit>]]>
-</programlisting>
+</programlisting>-->
<note>
- <para>
+<!-- <para>
This step is no longer necessary if Hibernate Annotation or EntityManager 3.3.x are used.
- </para>
+ </para>--> <para>When using Hibernate Search 3.1.x, more event listeners are required, but these are registered automa5tically by Hibernate Annotations. Refer to the <citetitle>Hibernate Search Reference Guide</citetitle> to learn to configure event listeners without using Hibernate EntityManager and Hibernate Annotations.</para>
</note>
<para>
The following <filename>JAR</filename>s must be deployed alongside the configuration file:
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/I18n.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/I18n.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/I18n.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -7,6 +7,9 @@
<para>
There are several stages required to internationalize and localize your application.
</para>
+ <note>
+ <para>Internationalization features are available only in the JSF context.</para>
+ </note>
<section>
<title>Internationalizing your application</title>
<para>
@@ -18,7 +21,7 @@
<section>
<title>Application server configuration</title>
<para>
- You will need to configure the Tomcat connector to ensure that the application server receives the request parameters from client requests in the correct encoding. If you use Tomcat or JBoss AS, add the <literal>URIEncoding="UTF-8"</literal> attribute to the connector configuration. For JBoss AS 4.2, edit <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/server. xml</literal>:
+ You will need to configure the Tomcat connector to ensure that the application server receives the request parameters from client requests in the correct encoding. Add the <literal>URIEncoding="UTF-8"</literal> attribute to the connector configuration in <filename>$JBOSS_HOME/server/$PROFILE/deploy/jboss-web.deployer/server.xml</filename>:
</para>
<programlisting role="XML"><![CDATA[<Connector port="8080" URIEncoding="UTF-8"/>]]>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Itext.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Itext.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Itext.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -356,6 +356,51 @@
</programlisting>
</entry>
</row>
+ <row>
+ <entry valign="top">
+ <para>
+ <literal><p:textcolumn></literal>
+ </para>
+ </entry>
+ <entry valign="top">
+ <para>
+ <emphasis>Description</emphasis>
+ </para>
+ <para><literal>p:textcolumn</literal> inserts a text column that can
+ be used to control the flow of text. The most common case is to
+ support right to left direction fonts.</para>
+ <para>
+ <emphasis>Attributes</emphasis>
+ <itemizedlist>
+ <listitem>
+ <para><literal>left</literal> — The left bounds of
+ the text column</para>
+ </listitem>
+ <listitem>
+ <para><literal>right</literal> — The right bounds
+ of the text column</para>
+ </listitem>
+ <listitem>
+ <para><literal>direction</literal> — The run direction
+ of the text in the column: <literal>RTL</literal>,
+ <literal>LTR</literal>, <literal
+ >NO-BIDI</literal>, <literal>DEFAULT</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ <emphasis>Usage</emphasis>
+ </para>
+ <programlisting role="XHTML"><![CDATA[
+<p:textcolumn left="400" right="600" direction="rtl">
+<p:font name="/Library/Fonts/Arial Unicode.ttf"
+encoding="Identity-H"
+embedded="true">#{phrases.arabic}</p:font>
+</p:textcolumn>]]></programlisting>
+ </entry>
+ </row>
+
<row>
<entry valign="top">
<para>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Mail.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Mail.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Mail.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -319,11 +319,10 @@
You can still use <literal>mail-ra.rar</literal> if you are not using JBoss AS, but your application server may include a similar adapter file.
</para>
- <note>
- <title>Note</title>
- <para>Distributed mail-ra.rar in Seam is designated as a technology preview so standard support is not guaranteed.
- </para>
- </note>
+ <warning>
+ <title>Distributed <filename>mail-ra.rar</filename> is a Technology Preview</title>
+ <para>Technology Preview features are not fully supported under Red Hat subscription level agreements (SLAs), may not be functionally complete, and are not intended for production use. However, these features provide early access to upcoming product innovations, enabling customers to test functionality and provide feedback during the development process. As Red Hat considers making future iterations of Technology Preview features generally available, we will provide commercially reasonable efforts to resolve any reported issues that customers experience when using these features.</para>
+ </warning>
</section>
@@ -383,7 +382,7 @@
</section>
- <section>
+ <!--<section>
<title>Meldware</title>
<para>
Meldware (from <ulink url="http://buni.org">buni.org</ulink>) is used as a mail server in Seam's mail examples. Meldware is a groupware package that provides <literal>SMTP</literal>, <literal>POP3</literal>, <literal>IMAP</literal>, webmail, a shared calendar and an graphical administration tool. It is written as a Java EE application, so it can be deployed onto JBoss AS alongside your Seam application.
@@ -393,7 +392,7 @@
The version of Meldware distributed with Seam (downloaded on demand) is tailored for development — mailboxes, users and aliases (email addresses) are created every time the application deploys. To use Meldware in production, install the latest release from <ulink url="http://buni.org">buni.org</ulink>.
</para>
</warning>
- </section>
+ </section>-->
<section id="mail.tags">
<title>Tags</title>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Preface.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Preface.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -123,14 +123,14 @@
</para>
</listitem>
</varlistentry>
- <varlistentry>
+<!-- <varlistentry>
<term><emphasis>Get started now!</emphasis></term>
<listitem>
<para>
Seam works in any Java EE application server. Even if your environment does not support EJB3, you can use Seam's inbuilt transaction management with JPA or Hibernate3 for persistence, or deploy Embedded JBoss in Tomcat for full EJB3 support.
</para>
</listitem>
- </varlistentry>
+ </varlistentry>-->
</variablelist>
<mediaobject>
<imageobject>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Security.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Security.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -4618,6 +4618,11 @@
<section>
<title>OpenID</title>
+ <warning>
+ <title>OpenID integration is a Technology Preview</title>
+ <para>Technology Preview features are not fully supported under Red Hat subscription level agreements (SLAs), may not be functionally complete, and are not intended for production use. However, these features provide early access to upcoming product innovations, enabling customers to test functionality and provide feedback during the development process. As Red Hat considers making future iterations of Technology Preview features generally available, we will provide commercially reasonable efforts to resolve any reported issues that customers experience when using these features.</para>
+ </warning>
+
<para>
OpenID is a community standard for external web-based authentication. Any web application can supplement (or replace) its local authentication handling by delegating responsibility to an external OpenID server selected by the user. This benefits both user and developer — the user (who no longer needs to remember login details for multiple web applications), and the developer (who need not maintain an entire complex authentication system).
</para>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Testing.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Testing.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Testing.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -418,7 +418,7 @@
<section>
<title>Integration Testing with Mock Data</title>
<para>
- If you want to insert or clean data in your database before each test, you can use Seam's integration with DBUnit. To do this, extend DBUnitSeamTest rather than <literal>SeamTest</literal>.
+ To insert or clean data in your database before each test, you can use Seam's integration with DBUnit. To do this, extend DBUnitSeamTest rather than <literal>SeamTest</literal>.
</para>
<para>
You must provide a dataset for DBUnit.
@@ -461,8 +461,7 @@
You need to tell DBUnit about your datasource by setting a TestNG test parameter named <literal>datasourceJndiName</literal>:
</para>
-<programlisting role="XML"><![CDATA[<parameter name="datasourceJndiName" value="java:/seamdiscsDatasource"/>]]>
-</programlisting>
+<programlisting role="XML"><![CDATA[<parameter name="datasourceJndiName" value="java:/seamdiscsDatasource"/>]]></programlisting>
<para>
DBUnitSeamTest supports both MySQL and HSQL. You must tell it which database is being used, otherwise it defaults to HSQL:
</para>
Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml 2010-02-09 02:23:15 UTC (rev 100729)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml 2010-02-09 03:33:00 UTC (rev 100730)
@@ -30,18 +30,18 @@
</listitem>
</itemizedlist>
<para>
- The example applications run both on JBoss AS and Tomcat with no additional configuration. The following sections will explain the procedure in both cases. Note that all examples are built and run from the Ant <filename>build.xml</filename>, so you will need a recent version of Ant installed before you get started.
+ Note that all examples are built and run from the Ant <filename>build.xml</filename>, so you will need a recent version of Ant installed before you get started.
</para>
<section>
<title>Running the examples on JBoss AS</title>
<para>
- The examples are configured for use on JBoss AS 4.2 or 5.0. You will need to set <literal>jboss.home</literal>, in the shared <filename>build.properties</filename> file (in the root folder of your Seam installation) to the location of your JBoss AS installation.
+ The examples are configured for use on JBoss Enterprise Application Platform. You will need to set <literal>jboss.home</literal>, in the shared <filename>build.properties</filename> file (in the root folder of your Seam installation) to the location of your JBoss AS installation.
</para>
<para>
Once you have set the location of JBoss AS and started the application server, you can build and deploy any example by typing <literal>ant explode</literal> in that example's directory. Any example that is packaged as an EAR (Enterprise Archive) deploys to a URL like <literal>/seam-<replaceable>example</replaceable></literal>, where <replaceable>example</replaceable> is the name of the example folder, with one exception: if the example folder begins with "seam", the prefix "seam" is ommitted. For instance, if JBoss AS is running on port 8080, the URL for the Registration example is <ulink url="http://localhost:8080/seam-registration/"> <literal>http://localhost:8080/seam-registration/</literal></ulink>, whereas the URL for the SeamSpace example is <ulink url="http://localhost:8080/seam-space/"> <literal>http://localhost:8080/seam-space/</literal></ulink>.
</para>
<para>
- If, on the other hand, the example is packaged as a WAR, then it deploys to a URL like <literal>/jboss-seam-<replaceable>example</replaceable></literal>. Most of the examples can be deployed as a WAR to Tomcat with Embedded JBoss by typing <literal>ant tomcat.deploy</literal>.
+ If, on the other hand, the example is packaged as a WAR, then it deploys to a URL like <literal>/jboss-seam-<replaceable>example</replaceable></literal>. <!--Most of the examples can be deployed as a WAR to Tomcat with Embedded JBoss by typing <literal>ant tomcat.deploy</literal>.-->
</para>
<note>
<para>
More information about the jboss-cvs-commits
mailing list