[jboss-cvs] JBossAS SVN: r100680 - in projects/docs/enterprise/EWP_5.0: Seam_Reference_Guide/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 8 01:19:40 EST 2010
Author: laubai
Date: 2010-02-08 01:19:40 -0500 (Mon, 08 Feb 2010)
New Revision: 100680
Modified:
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Alternatives.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Configuration.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Excel.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Gwt.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/I18n.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Itext.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Mail.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Security.xml
projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Testing.xml
Log:
Corrected directory structure.
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Alternatives.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Alternatives.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Alternatives.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -37,7 +37,6 @@
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.
+ Two server profiles will be included in your installation - <emphasis>default</emphasis> and <emphasis>production</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 Web Platform.
</para>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -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_Web_Platform/5.0.0/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>.
</para>
</section>
</section>
Modified: projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Configuration.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Configuration.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -960,12 +960,10 @@
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>
+ <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>
</section>
<section>
Modified: projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Excel.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Excel.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Excel.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -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/EWP_5.0/Seam_Reference_Guide/en-US/Gwt.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Gwt.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Gwt.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -4,6 +4,12 @@
<chapter id="gwt" lang="en-US">
<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 +17,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/EWP_5.0/Seam_Reference_Guide/en-US/I18n.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/I18n.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/I18n.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -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>
Modified: projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Itext.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Itext.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Itext.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -356,6 +356,50 @@
</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/EWP_5.0/Seam_Reference_Guide/en-US/Mail.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Mail.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Mail.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -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>
@@ -648,4 +647,4 @@
</section>
</chapter>
-
+
Modified: projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Security.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Security.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -4618,6 +4618,12 @@
<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/EWP_5.0/Seam_Reference_Guide/en-US/Testing.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Testing.xml 2010-02-08 05:28:20 UTC (rev 100679)
+++ projects/docs/enterprise/EWP_5.0/Seam_Reference_Guide/en-US/Testing.xml 2010-02-08 06:19:40 UTC (rev 100680)
@@ -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>
More information about the jboss-cvs-commits
mailing list