[seam-commits] Seam SVN: r11660 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Mon Nov 23 22:47:48 EST 2009
Author: laubai
Date: 2009-11-23 22:47:48 -0500 (Mon, 23 Nov 2009)
New Revision: 11660
Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml
Log:
Edited groovy, hsearch, i18n chapters.
Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml 2009-11-24 03:39:31 UTC (rev 11659)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml 2009-11-24 03:47:48 UTC (rev 11660)
@@ -5,10 +5,9 @@
<title>Groovy integration</title>
<para>One aspect of JBoss Seam is its RAD (Rapid Application Development) capability. While not synonymous with RAD,
- one interesting tool in this space is dynamic languages. Until recently, choosing a dynamic language was
- required choosing a completely different development platform (a development platform with a set of APIs and a
- runtime so great that you would no longer want to use you old legacy Java [sic] APIs anymore, which would be
- lucky because you would be forced to use those proprietary APIs anyway). Dynamic languages built on top of the
+ one interesting tool in this space is dynamic languages. Until recently, choosing a dynamic language
+ required choosing a completely different development platform with a different set of Java APIs.
+ Dynamic languages built on top of the
Java Virtual Machine, and <ulink url="http://groovy.codehaus.org">Groovy</ulink> in particular broke this
approach in silos.</para>
@@ -46,8 +45,8 @@
<section>
<title>Writing Seam applications in Groovy</title>
- <para>There is not much to say about it. Since a Groovy object is a Java object, you can virtually write any
- Seam component, or any class for what it worth, in Groovy and deploy it. You can also mix Groovy classes and
+ <para>Since a Groovy object is a Java object, you can virtually write any
+ Seam component, or any class, in Groovy and deploy it. You can also mix Groovy classes and
Java classes in the same application.</para>
<section>
@@ -94,7 +93,7 @@
}
}</programlisting>
- <para>Groovy natively support the notion of properties (getter/setter), so there is no need to
+ <para>Groovy natively supports the notion of properties (getter/setter), so there is no need to
explicitly write verbose getters and setters: in the previous example, the hotel class can be
accessed from Java as <code>hotel.getCity()</code>, the getters and setters being generated by the
Groovy compiler. This type of syntactic sugar makes the entity code very concise.</para>
@@ -143,7 +142,7 @@
<section>
<title>seam-gen</title>
- <para>Seam gen has a transparent integration with Groovy. You can write Groovy code in seam-gen backed
+ <para>Seam gen itegrates transparently with Groovy. You can write Groovy code in seam-gen backed
projects without any additional infrastructure requirement. When writing a Groovy entity, simply place
your <filename>.groovy</filename> files in <filename>src/model</filename>. Unsurprisingly, when writing
an action, simply place your <filename>.groovy</filename> files in
@@ -166,10 +165,10 @@
<title>Deploying Groovy code</title>
<para>A Groovy class <emphasis>is</emphasis> a Java class, with a bytecode representation just like a Java
- class. To deploy, a Groovy entity, a Groovy Session bean or a Groovy Seam component, a compilation step
+ class. To deploy a Groovy entity, a Groovy Session bean or a Groovy Seam component, a compilation step
is necessary. A common approach is to use the <literal>groovyc</literal> ant task. Once compiles, a
Groovy class is in no way different than a Java class and the application server will treat them
- equally. Note that this allow a seamless mix of Groovy and Java code.</para>
+ equally. Note that this allows a seamless mix of Groovy and Java code.</para>
</section>
<section>
@@ -183,7 +182,7 @@
incrementally with no need to restart the application (and obviously not the application server either).</para>
<para>Be aware that the native .groovy file deployment suffers the same limitations as the regular Seam
- hotdeployment:</para>
+ hot deployment:</para>
<itemizedlist>
<listitem>
Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml 2009-11-24 03:39:31 UTC (rev 11659)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml 2009-11-24 03:47:48 UTC (rev 11660)
@@ -7,24 +7,23 @@
<section>
<title>Introduction</title>
- <para>Full text search engines like Apache Lucene™ are a very powerful
+ <para>Full text search engines like Apache Lucene are a very powerful
technology that bring full text and efficient queries to applications.
Hibernate Search, which uses Apache Lucene under the covers, indexes your
domain model with the addition of a few annotations, takes care of the
database / index synchronization and returns regular managed objects that
- are matched by full text queries. Keep in mind, thought, that there are
+ are matched by full text queries. Keep in mind, though, that there are
mismatches that arise when dealing with an object domain model over a text
index (keeping the index up to date, mismatch between the index structure
and the domain model, and querying mismatch). But the benefits of speed
and efficiency far outweigh these limitations.</para>
- <para>Hibernate Search has been designed to integrates nicely and as
+ <para>Hibernate Search has been designed to integrate as
naturally as possible with JPA and Hibernate. As a natural extension,
JBoss Seam provides an Hibernate Search integration.</para>
- <para>Please refer to the <ulink
- url="http://www.hibernate.org/hib_docs/search/reference/en/html_single/">Hibernate
- Search documentation</ulink> for information specific to the Hibernate
+ <para>Please refer to the Hibernate Search documentation provided with this release
+ of JBoss Enterprise Application Platform for information specific to the Hibernate
Search project.</para>
<note>
@@ -60,7 +59,7 @@
</persistence-unit>]]></programlisting>
<para>If you plan to target Hibernate Annotations or EntityManager 3.2.x
- (embedded into JBoss EAP AS 4.3), you also need to configure the
+ (embedded into JBoss Enterprise Application Platform 4.3), you also need to configure the
appropriate event listeners.</para>
<programlisting role="XML"><![CDATA[<persistence-unit name="sample">
@@ -115,10 +114,8 @@
<section>
<title>Usage</title>
- <para>Hibernate Search uses annotations to map entities to a Lucene index,
- check the <ulink
- url="http://www.hibernate.org/hib_docs/search/reference/en/html_single/">reference
- documentation</ulink> for more informations.</para>
+ <para>Hibernate Search uses annotations to map entities to a Lucene index. For more information,
+ see the Hibernate Reference Guide provided with this release.</para>
<para>Hibernate Search is fully integrated with the API and semantic of
JPA / Hibernate. Switching from a HQL or Criteria based query requires
Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml 2009-11-24 03:39:31 UTC (rev 11659)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml 2009-11-24 03:47:48 UTC (rev 11660)
@@ -7,21 +7,21 @@
<para>
Seam makes it easy to build internationalized applications. First, let's
walk through all the stages needed to internationalize and localize your
- app. Then we'll take a look at the components Seam bundles.
+ application. Then we'll take a look at the component Seam bundles.
</para>
<section>
- <title>Internationalizing your app</title>
+ <title>Internationalizing your application</title>
<para>
- A JEE application consists of many components and all of them must be
+ A Java EE application consists of many components and all of them must be
configured properly for your application to be localized.
</para>
<para>
Starting at the bottom, the first step is to ensure that your database
- server and client is using the correct character encoding for your
- locale. Normally you'll want to use UTF-8. How to do this is outside
+ server and client uses the correct character encoding for your
+ locale. Normally you will want to use UTF-8. How to do this is outside
the scope of this tutorial.
</para>
@@ -104,8 +104,8 @@
To set the display character encoding, you need to use the
<literal><f:view locale="cs_CZ"/></literal> tag (here we tell
JSF to use the Czech locale). You may want to change the encoding of
- the xml document itself if you want to embed localized strings in the
- xml. To do this alter the encoding attribute in xml declaration
+ the XML document itself if you want to embed localized strings in the
+ XML. To do this alter the encoding attribute in XML declaration
<literal><?xml version="1.0" encoding="UTF-8"?></literal> as
required.
</para>
@@ -129,7 +129,7 @@
<para>Each user login session has an associated instance of
<literal>java.util.Locale</literal> (available to the application as a
component named <literal>locale</literal>). Under normal circumstances,
- you won't need to do any special configuration to set the locale. Seam
+ you will not need to do any special configuration to set the locale. Seam
just delegates to JSF to determine the active locale:</para>
<itemizedlist>
@@ -190,7 +190,7 @@
<para>JSF supports internationalization of user interface labels and
descriptive text via the use of <literal><f:loadBundle /></literal>.
You can use this approach in Seam applications. Alternatively, you can
- take advantage of the Seam <literal> messages</literal> component to
+ take advantage of the Seam <literal>messages</literal> component to
display templated labels with embedded EL expressions.</para>
<section>
@@ -202,9 +202,7 @@
internationalized labels available via this special resource bundle. By
default, the resource bundle used by Seam is named
<literal>messages</literal> and so you'll need to define your labels in
- files named <literal> messages.properties</literal>, <literal>
- messages_en.properties</literal>, <literal>
- messages_en_AU.properties</literal>, etc. These files usually belong in
+ files named <literal>messages.properties</literal>, <literal>messages_en.properties</literal>, <literal>messages_en_AU.properties</literal>, etc. These files usually belong in
the <literal>WEB-INF/classes</literal> directory.</para>
<para>So, in <literal>messages_en.properties</literal>:</para>
@@ -230,7 +228,7 @@
<para>If you want to define a message just for a particular page, you
can specify it in a resource bundle with the same name as the JSF view
- id, with the leading <literal>/</literal> and trailing file extension
+ ID, with the leading <literal>/</literal> and trailing file extension
removed. So we could put our message in <literal>
welcome/hello_en.properties</literal> if we only needed to display the
message on <literal> /welcome/hello.jsp</literal>.</para>
@@ -334,7 +332,9 @@
</theme:available-themes>
</theme:theme-selector></programlisting>
- <para>Note that the first theme listed is the default theme.</para>
+ <note>
+ <para>The first theme listed is the default theme.</para>
+ </note>
<para>Themes are defined in a properties file with the same name as the
theme. For example, the <literal>default</literal> theme is defined as a
More information about the seam-commits
mailing list