[hibernate-commits] Hibernate SVN: r19521 - validator/trunk/hibernate-validator/src/main/docbook/en-US/modules.
hibernate-commits at lists.jboss.org
hibernate-commits at lists.jboss.org
Sat May 15 08:33:10 EDT 2010
Author: gunnar.morling
Date: 2010-05-15 08:33:09 -0400 (Sat, 15 May 2010)
New Revision: 19521
Modified:
validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/customconstraints.xml
validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/furtherreading.xml
validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/gettingstarted.xml
validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/integration.xml
validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/usingvalidator.xml
validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/xmlconfiguration.xml
Log:
HV-298: Fixed some typos and dangling references
Modified: validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/customconstraints.xml
===================================================================
--- validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/customconstraints.xml 2010-05-15 12:27:18 UTC (rev 19520)
+++ validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/customconstraints.xml 2010-05-15 12:33:09 UTC (rev 19521)
@@ -134,10 +134,10 @@
<listitem>
<para>an attribute <classname>payload</classname> that can be used
- by clients of the Bean Validation API to asign custom payload
+ by clients of the Bean Validation API to assign custom payload
objects to a constraint. This attribute is not used by the API
itself. <tip>
- <para>An examle for a custom payload could be the definition of
+ <para>An example for a custom payload could be the definition of
a severity.</para>
<programlisting>public class Severity {
@@ -165,7 +165,7 @@
</itemizedlist>
<para>Besides those three mandatory attributes
- (<property>messge</property>, <property>groups</property> and
+ (<property>message</property>, <property>groups</property> and
<property>payload</property>) we add another one allowing for the
required case mode to be specified. The name <property>value</property>
is a special one, which can be omitted upon using the annotation, if it
@@ -267,7 +267,7 @@
<classname>initialize()</classname>. As the Bean Validation
specification recommends, we consider <code>null</code> values as being
valid. If <code>null</code> is not a valid value for an element, it
- should be annotated with <code>@NotNull</code> explicitely.</para>
+ should be annotated with <code>@NotNull</code> explicitly.</para>
<section>
<title>The ConstraintValidatorContext</title>
Modified: validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/furtherreading.xml
===================================================================
--- validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/furtherreading.xml 2010-05-15 12:27:18 UTC (rev 19520)
+++ validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/furtherreading.xml 2010-05-15 12:33:09 UTC (rev 19521)
@@ -35,7 +35,7 @@
itself is also a great way to deepen your understanding of Bean Validation
resp. Hibernate Validator.</para>
- <para>If you have any furhter questions to Hibernate Validator or want to
+ <para>If you have any further questions to Hibernate Validator or want to
share some of your use cases have a look at the <ulink
url="http://community.jboss.org/en/hibernate/validator">Hibernate Validator
Wiki</ulink> and the <ulink
Modified: validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/gettingstarted.xml
===================================================================
--- validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/gettingstarted.xml 2010-05-15 12:27:18 UTC (rev 19520)
+++ validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/gettingstarted.xml 2010-05-15 12:33:09 UTC (rev 19521)
@@ -70,7 +70,7 @@
<note>
<para>Hibernate Validator uses JAXB for XML parsing. JAXB is part of the
Java Class Library since Java 6 which means that if you run Hibernate
- Validator with Java 5 you will have to add additional JAXB dependecies.
+ Validator with Java 5 you will have to add additional JAXB dependencies.
Using maven you have to add the following dependencies:<programlisting><dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
Modified: validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/integration.xml
===================================================================
--- validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/integration.xml 2010-05-15 12:27:18 UTC (rev 19520)
+++ validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/integration.xml 2010-05-15 12:33:09 UTC (rev 19521)
@@ -59,7 +59,7 @@
<para>You can also limit the DDL constraint generation to a subset of the
defined constraints by setting the property
<property>org.hibernate.validator.group.ddl</property>. The property
- specifies the comma seperated, fully specified classnames of the groups a
+ specifies the comma-separated, fully specified class names of the groups a
constraint has to be part of in order to be considered for DDL schema
generation.</para>
</section>
@@ -88,7 +88,7 @@
<property>javax.persistence.validation.group.pre-persist</property>,
<property>javax.persistence.validation.group.pre-update</property> and
<property>javax.persistence.validation.group.pre-remove</property>. The
- values of these properties are the comma seperated, fully specified
+ values of these properties are the comma-separated, fully specified
class names of the groups to validate. <xref
linkend="example-beanvalidationeventlistener-config" /> shows the
default values for these properties. In this case they could also be
@@ -171,7 +171,7 @@
<para>When working with JSF2 or <productname>JBoss Seam</productname> and
Hibernate Validator (Bean Validation) is present in the runtime
environment validation is triggered for every field in the application.
- <xref linkend="example-jsf" /> shows an example of the f:validateBean tag
+ <xref linkend="example-jsf2" /> shows an example of the f:validateBean tag
in a JSF page. For more information refer to the Seam documentation or the
JSF 2 specification.</para>
Modified: validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/usingvalidator.xml
===================================================================
--- validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/usingvalidator.xml 2010-05-15 12:27:18 UTC (rev 19520)
+++ validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/usingvalidator.xml 2010-05-15 12:33:09 UTC (rev 19521)
@@ -79,8 +79,9 @@
</example>
<para>When using field level constraints field access strategy is used
- to access the value to be validated. This means the instance variable
- directly independed of the access type.</para>
+ to access the value to be validated. This means the bean validation
+ provider directly accesses the instance variable and does not invoke the
+ property accessor method also if such a method exists.</para>
<note>
<para>The access type (private, protected or public) does not
@@ -248,8 +249,7 @@
}</programlisting>
</example>
- <para>Our well-known class <classname>Car</classname> from <xref
- linkend="example-class-car" /> is now extended by
+ <para>Our well-known class <classname>Car</classname> is now extended by
<classname>RentalCar</classname> with the additional property
<property>rentalStation</property>. If an instance of
<classname>RentalCar</classname> is validated, not only the
@@ -337,11 +337,11 @@
<code>null</code>.</para>
<para>Object graph validation also works for collection-typed fields.
- That means any attributes that are</para>
+ That means any attributes that</para>
<itemizedlist>
<listitem>
- <para>arrays</para>
+ <para>are arrays</para>
</listitem>
<listitem>
@@ -545,7 +545,7 @@
<entry>Usage</entry>
- <entry>Example (refering to <xref
+ <entry>Example (referring to <xref
linkend="example-validator-validate" />)</entry>
</row>
</thead>
@@ -892,7 +892,7 @@
<note>
<para>If at least one constraints fails in a sequenced group none of
- the constraints of the follwoing groups in the sequence get
+ the constraints of the following groups in the sequence get
validated.</para>
</note>
@@ -1354,10 +1354,10 @@
<entry>field/property. Any non-primitive types are
supported.</entry>
- <entry>Performs validation recursively on the associated object. If
- the object is a collection or an array, the elements are validated
- recursively. If the object is a map, the value elements are
- validated recursively.</entry>
+ <entry>Performs validation recursively on the associated object.
+ If the object is a collection or an array, the elements are
+ validated recursively. If the object is a map, the value elements
+ are validated recursively.</entry>
<entry>none</entry>
</row>
Modified: validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/xmlconfiguration.xml
===================================================================
--- validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/xmlconfiguration.xml 2010-05-15 12:27:18 UTC (rev 19520)
+++ validator/trunk/hibernate-validator/src/main/docbook/en-US/modules/xmlconfiguration.xml 2010-05-15 12:33:09 UTC (rev 19521)
@@ -86,7 +86,7 @@
<classname>javax.validation.ConstraintValidatorFactory</classname>. The
same configuration options are also available programmatically through the
<classname>javax.validation.Configuration</classname>. In fact XML
- configuration will be overriden by values explicitly specified via the
+ configuration will be overridden by values explicitly specified via the
API. It is even possible to ignore the XML configuration completely via
<methodname> Configuration.ignoreXmlConfiguration()</methodname>. See also
<xref linkend="validator-bootstrapping" />.</para>
More information about the hibernate-commits
mailing list