# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2013-04-29 13:14+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#: integration.xml:24
#, no-c-format
msgid "Integrating with other frameworks"
msgstr ""

#. Tag: para
#: integration.xml:26
#, no-c-format
msgid "Hibernate Validator is intended to be used to implement multi-layered data validation, where constraints are expressed in a single place (the annotated domain model) and checked in various different layers of the application."
msgstr ""

#. Tag: title
#: integration.xml:32
#, no-c-format
msgid "OSGi"
msgstr ""

#. Tag: para
#: integration.xml:34
#, no-c-format
msgid "The Hibernate Validator jar file is conform to the OSGi specification and can be used within any OSGi container. The following lists represent the packages imported and exported by Hibernate Validator. The classes within the exported packages are considered part of Hibernate Validator public API."
msgstr ""

#. Tag: para
#: integration.xml:41
#, no-c-format
msgid "The Java Service Provider mechanism used by Bean Validation to automatically discover validation providers doesn't work in an OSGi environment. To solve this, you have to provide a custom <classname>ValidationProviderResolver</classname> (see <xref linkend=\"section-validation-provider-resolver\"/>)."
msgstr ""

#. Tag: title
#: integration.xml:49
#, no-c-format
msgid "Exported packages"
msgstr ""

#. Tag: package
#: integration.xml:52
#, no-c-format
msgid "org.hibernate.validator"
msgstr ""

#. Tag: package
#: integration.xml:56
#, no-c-format
msgid "org.hibernate.validator.cfg.*"
msgstr ""

#. Tag: package
#: integration.xml:60
#, no-c-format
msgid "org.hibernate.validator.constraints.*"
msgstr ""

#. Tag: package
#: integration.xml:64
#, no-c-format
msgid "org.hibernate.validator.group"
msgstr ""

#. Tag: package
#: integration.xml:68
#, no-c-format
msgid "org.hibernate.validator.messageinterpolation"
msgstr ""

#. Tag: package
#: integration.xml:72
#, no-c-format
msgid "org.hibernate.validator.resourceloading"
msgstr ""

#. Tag: package
#: integration.xml:76
#, no-c-format
msgid "org.hibernate.validator.spi.*"
msgstr ""

#. Tag: title
#: integration.xml:81
#, no-c-format
msgid "Imported packages"
msgstr ""

#. Tag: para
#: integration.xml:84
#, no-c-format
msgid "<package>javax.persistence.*</package>, [2.0.0,3.0.0), optional"
msgstr ""

#. Tag: para
#: integration.xml:89
#, no-c-format
msgid "<package>javax.validation.*</package>, [1.0.0,2.0.0)"
msgstr ""

#. Tag: package
#: integration.xml:93
#, no-c-format
msgid "javax.xml.*"
msgstr ""

#. Tag: para
#: integration.xml:97
#, no-c-format
msgid "<package>javax.el.*</package>, [2.0.0,4.0.0)"
msgstr ""

#. Tag: package
#: integration.xml:101
#, no-c-format
msgid "org.xml.sax.*"
msgstr ""

#. Tag: para
#: integration.xml:105
#, no-c-format
msgid "<package>org.jboss.logging.*</package>, [3.1.0,4.0.0)"
msgstr ""

#. Tag: para
#: integration.xml:109
#, no-c-format
msgid "<package>com.fasterxml.classmate.*</package>, 0.8.0"
msgstr ""

#. Tag: para
#: integration.xml:113
#, no-c-format
msgid "<package>org.joda.time.*</package>, [1.6.0,2.0.0), optional"
msgstr ""

#. Tag: para
#: integration.xml:118
#, no-c-format
msgid "<package>org.jsoup.*</package>, [1.5.2,2.0.0), optional"
msgstr ""

#. Tag: title
#: integration.xml:124
#, no-c-format
msgid "Database schema-level validation"
msgstr ""

#. Tag: para
#: integration.xml:126
#, no-c-format
msgid "Out of the box, Hibernate Annotations (as of Hibernate 3.5.x) will translate the constraints you have defined for your entities into mapping metadata. For example, if a property of your entity is annotated <literal>@NotNull</literal>, its columns will be declared as <literal>not null</literal> in the DDL schema generated by Hibernate."
msgstr ""

#. Tag: para
#: integration.xml:132
#, no-c-format
msgid "If, for some reason, the feature needs to be disabled, set <literal>hibernate.validator.apply_to_ddl</literal> to <literal>false</literal>. See also <xref linkend=\"table-spec-constraints\"/> and <xref linkend=\"table-custom-constraints\"/>."
msgstr ""

#. Tag: para
#: integration.xml:138
#, no-c-format
msgid "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-separated, fully specified class names of the groups a constraint has to be part of in order to be considered for DDL schema generation."
msgstr ""

#. Tag: title
#: integration.xml:147
#, no-c-format
msgid "ORM integration"
msgstr ""

#. Tag: para
#: integration.xml:149
#, no-c-format
msgid "Hibernate Validator integrates with both Hibernate and all pure Java Persistence providers."
msgstr ""

#. Tag: para
#: integration.xml:153
#, no-c-format
msgid "When lazy loaded associations are supposed to be validated it is recommended to place the constraint on the getter of the association. Hibernate replaces lazy loaded associations with proxy instances which get initialized/loaded when requested via the getter. If, in such a case, the constraint is placed on field level the actual proxy instance is used which will lead to validation errors."
msgstr ""

#. Tag: title
#: integration.xml:162
#, no-c-format
msgid "Hibernate event-based validation"
msgstr ""

#. Tag: para
#: integration.xml:164
#, no-c-format
msgid "Hibernate Validator has a built-in Hibernate event listener - <ulink url=\"http://fisheye.jboss.org/browse/Hibernate/core/trunk/annotations/src/main/java/org/hibernate/cfg/beanvalidation/BeanValidationEventListener.java\"><classname>org.hibernate.cfg.beanvalidation.BeanValidationEventListener</classname></ulink> - which is part of Hibernate Annotations (as of Hibernate 3.5.x). Whenever a <literal>PreInsertEvent</literal>, <literal>PreUpdateEvent</literal> or <classname>PreDeleteEvent</classname> occurs, the listener will verify all constraints of the entity instance and throw an exception if any constraint is violated. Per default objects will be checked before any inserts or updates are made by Hibernate. Pre deletion events will per default not trigger a validation. You can configure the groups to be validated per event type using the properties <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-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 omitted."
msgstr ""

#. Tag: para
#: integration.xml:185
#, no-c-format
msgid "On constraint violation, the event will raise a runtime <classname>ConstraintViolationException</classname> which contains a set of <literal>ConstraintViolation</literal>s describing each failure."
msgstr ""

#. Tag: para
#: integration.xml:190
#, no-c-format
msgid "If Hibernate Validator is present in the classpath, Hibernate Annotations (or Hibernate EntityManager) will use it transparently. To avoid validation even though Hibernate Validator is in the classpath set <property>javax.persistence.validation.mode</property> to <constant>none</constant>."
msgstr ""

#. Tag: para
#: integration.xml:197
#, no-c-format
msgid "If the beans are not annotated with validation annotations, there is no runtime performance cost."
msgstr ""

#. Tag: para
#: integration.xml:201
#, no-c-format
msgid "In case you need to manually set the event listeners for Hibernate Core, use the following configuration in <literal>hibernate.cfg.xml</literal>:"
msgstr ""

#. Tag: title
#: integration.xml:206
#, no-c-format
msgid "Manual configuration of <classname>BeanValidationEvenListener</classname>"
msgstr ""

#. Tag: programlisting
#: integration.xml:209
#, no-c-format
msgid ""
      "&lt;hibernate-configuration&gt;\n"
      "    &lt;session-factory&gt;\n"
      "       ...\n"
      "       &lt;property name=\"javax.persistence.validation.group.pre-persist\"&gt;javax.validation.groups.Default&lt;/property&gt;\n"
      "       &lt;property name=\"javax.persistence.validation.group.pre-update\"&gt;javax.validation.groups.Default&lt;/property&gt;\n"
      "       &lt;property name=\"javax.persistence.validation.group.pre-remove\"&gt;&lt;/property&gt;\n"
      "       ...\n"
      "       &lt;event type=\"pre-update\"&gt;\n"
      "         &lt;listener class=\"org.hibernate.cfg.beanvalidation.BeanValidationEventListener\"/&gt;\n"
      "       &lt;/event&gt;\n"
      "       &lt;event type=\"pre-insert\"&gt;\n"
      "         &lt;listener class=\"org.hibernate.cfg.beanvalidation.BeanValidationEventListener\"/&gt;\n"
      "       &lt;/event&gt;\n"
      "       &lt;event type=\"pre-delete\"&gt;\n"
      "         &lt;listener class=\"org.hibernate.cfg.beanvalidation.BeanValidationEventListener\"/&gt;\n"
      "       &lt;/event&gt;\n"
      "    &lt;/session-factory&gt;\n"
      "&lt;/hibernate-configuration&gt;"
msgstr ""

#. Tag: title
#: integration.xml:214
#, no-c-format
msgid "<title>JPA</title>"
msgstr ""

#. Tag: para
#: integration.xml:216
#, no-c-format
msgid "If you are using JPA 2 and Hibernate Validator is in the classpath the JPA2 specification requires that Bean Validation gets enabled. The properties <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> as described in <xref linkend=\"validator-checkconstraints-orm-hibernateevent\"/> can in this case be configured in <filename>persistence.xml</filename>. <filename>persistence.xml</filename> also defines a node validation-mode which can be set to <constant>AUTO</constant>, <constant>CALLBACK</constant>, <constant>NONE</constant>. The default is <constant>AUTO</constant>."
msgstr ""

#. Tag: para
#: integration.xml:230
#, no-c-format
msgid "In a JPA 1 you will have to create and register Hibernate Validator yourself. In case you are using Hibernate EntityManager you can add a customized version of the <classname>BeanValidationEventListener</classname> described in <xref linkend=\"validator-checkconstraints-orm-hibernateevent\"/> to your project and register it manually."
msgstr ""

#. Tag: title
#: integration.xml:240
#, no-c-format
msgid "Presentation layer validation"
msgstr ""

#. Tag: para
#: integration.xml:242
#, no-c-format
msgid "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-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."
msgstr ""

#. Tag: title
#: integration.xml:250
#, no-c-format
msgid "Usage of Bean Validation within JSF2"
msgstr ""

#. Tag: programlisting
#: integration.xml:252
#, no-c-format
msgid ""
      "&lt;h:form&gt;\n"
      "  <emphasis role=\"bold\">&lt;f:validateBean&gt;</emphasis>\n"
      "    &lt;h:inputText value=”#{model.property}” /&gt;\n"
      "    &lt;h:selectOneRadio value=”#{model.radioProperty}” &gt; ... &lt;/h:selectOneRadio&gt;\n"
      "    &lt;!-- other input components here --&gt;\n"
      "  <emphasis role=\"bold\">&lt;/f:validateBean&gt;</emphasis>\n"
      "&lt;/h:form&gt;"
msgstr ""

#. Tag: para
#: integration.xml:256
#, no-c-format
msgid "The integration between JSF 2 and Bean Validation is described in the \"Bean Validation Integration\" chapter of <ulink url=\"http://jcp.org/en/jsr/detail?id=314\">JSR-314</ulink>. It is interesting to know that JSF 2 implements a custom MessageInterpolator to ensure ensure proper localization. To encourage the use of the Bean Validation message facility, JSF 2 will per default only display the generated Bean Validation message. This can, however, be configured via the application resource bundle by providing the following configuration (<parameter>{0}</parameter> is replaced with the Bean Validation message and <parameter>{1}</parameter> is replaced with the JSF component label):"
msgstr ""

#. Tag: programlisting
#: integration.xml:268
#, no-c-format
msgid "javax.faces.validator.BeanValidator.MESSAGE={1}: {0}"
msgstr ""

#. Tag: para
#: integration.xml:270
#, no-c-format
msgid "The default is:"
msgstr ""

#. Tag: programlisting
#: integration.xml:272
#, no-c-format
msgid "javax.faces.validator.BeanValidator.MESSAGE={0}"
msgstr ""

#. Tag: title
#: integration.xml:277
#, no-c-format
msgid "<title>CDI</title>"
msgstr ""

#. Tag: para
#: integration.xml:279
#, no-c-format
msgid "TODO"
msgstr ""
