Hibernate SVN: r12724 - in core/trunk/documentation/manual: fr-FR/src/main/docbook/modules and 1 other directories.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 02:05:53 -0400 (Wed, 04 Jul 2007)
New Revision: 12724
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/performance.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml
core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/performance.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml
Log:
[HHH-1116] batch-size typo
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/performance.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/performance.xml 2007-07-04 06:01:25 UTC (rev 12723)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/performance.xml 2007-07-04 06:05:53 UTC (rev 12724)
@@ -532,7 +532,7 @@
</class>]]></programlisting>
<para>
- With a <literal>batch-size</literal> of 8, Hibernate will load 3, 3, 3, 1 collections in four
+ With a <literal>batch-size</literal> of 3, Hibernate will load 3, 3, 3, 1 collections in four
<literal>SELECT</literal>s. Again, the value of the attribute depends on the expected number of
uninitialized collections in a particular <literal>Session</literal>.
</para>
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml 2007-07-04 06:01:25 UTC (rev 12723)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml 2007-07-04 06:05:53 UTC (rev 12724)
@@ -1211,7 +1211,7 @@
</para>
<para>
- Many developers program defensive and create a link management methods to
+ Many developers program defensive and create link management methods to
correctly set both sides, e.g. in <literal>Person</literal>:
</para>
Modified: core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/performance.xml
===================================================================
--- core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/performance.xml 2007-07-04 06:01:25 UTC (rev 12723)
+++ core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/performance.xml 2007-07-04 06:05:53 UTC (rev 12724)
@@ -563,7 +563,7 @@
</class>]]></programlisting>
<para>
- Avec une taille de lot (<literal>batch-size</literal>) de 8, Hibernate chargera
+ Avec une taille de lot (<literal>batch-size</literal>) de 3, Hibernate chargera
respectivement 3, 3, 3, et 1 collections en quatre <literal>SELECT</literal>s.
Encore une fois, la valeur de l'attribut d�pend du nombre de collections
non initialis�es dans une <literal>Session</literal> particuli�re.
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml 2007-07-04 06:01:25 UTC (rev 12723)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml 2007-07-04 06:05:53 UTC (rev 12724)
@@ -527,7 +527,7 @@
</class>]]></programlisting>
<para>
- Com um <literal>batch-size</literal>de 8, o Hibernate irá carregar 3, 3, 3, 1 coleções em 4
+ Com um <literal>batch-size</literal> de 3, o Hibernate irá carregar 3, 3, 3, 1 coleções em 4
<literal>SELECT</literal>s. Novamente, o valor do atributo depende do número esperado de coleções
não inicialiadas em determinada <literal>Session</literal>.
</para>
16 years, 10 months
Hibernate SVN: r12723 - core/trunk/documentation/manual/en-US/src/main/docbook/modules.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 02:01:25 -0400 (Wed, 04 Jul 2007)
New Revision: 12723
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml
Log:
[HHH-2487] Typo in "5.1.7. version (optional)"
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml 2007-07-04 05:59:40 UTC (rev 12722)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml 2007-07-04 06:01:25 UTC (rev 12723)
@@ -1376,7 +1376,7 @@
<para>
A version or timestamp property should never be null for a detached instance, so
- Hibernate will detact any instance with a null version or timestamp as transient,
+ Hibernate will detect any instance with a null version or timestamp as transient,
no matter what other <literal>unsaved-value</literal> strategies are specified.
<emphasis>Declaring a nullable version or timestamp property is an easy way to avoid
any problems with transitive reattachment in Hibernate, especially useful for people
16 years, 10 months
Hibernate SVN: r12722 - in core/trunk/documentation/manual: es-ES/src/main/docbook and 6 other directories.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 01:59:40 -0400 (Wed, 04 Jul 2007)
New Revision: 12722
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/master.xml
core/trunk/documentation/manual/es-ES/src/main/docbook/master.xml
core/trunk/documentation/manual/es-ES/src/main/docbook/modules/tutorial.xml
core/trunk/documentation/manual/fr-FR/src/main/docbook/master.xml
core/trunk/documentation/manual/ja-JP/src/main/docbook/master.xml
core/trunk/documentation/manual/ko-KR/src/main/docbook/master.xml
core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/tutorial.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/master.xml
Log:
[HHH-2417] Update book on Hibernate reference
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/master.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/master.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/master.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -100,11 +100,11 @@
<listitem>
<para>
Use this reference documentation as your primary source of information.
- Consider reading <emphasis>Hibernate in Action</emphasis>
- (http://www.manning.com/bauer) if you need more help with application
+ Consider reading <emphasis>Java Persistence with Hibernate</emphasis>
+ (http://www.manning.com/bauer2) if you need more help with application
design or if you prefer a step-by-step tutorial. Also visit
http://caveatemptor.hibernate.org and download the example application
- for Hibernate in Action.
+ for Java Persistence with Hibernate.
</para>
</listitem>
<listitem>
Modified: core/trunk/documentation/manual/es-ES/src/main/docbook/master.xml
===================================================================
--- core/trunk/documentation/manual/es-ES/src/main/docbook/master.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/es-ES/src/main/docbook/master.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -118,11 +118,11 @@
<listitem>
<para>
Usa esta documentación de referencia como tu fuente de información
- primaria. Ten en consideración leer <emphasis>Hibernate in Action</emphasis>
- (http://www.manning.com/bauer) si necesitas mas ayuda con el diseño
+ primaria. Ten en consideración leer <emphasis>Java Persistence with Hibernate</emphasis>
+ (http://www.manning.com/bauer2) si necesitas mas ayuda con el diseño
de aplicaciones o si prefieres un tutorial paso a paso.
Visita también http://caveatemptor.hibernate.org y descarga la aplicación
- de ejemplo para Hibernate in Action.
+ de ejemplo para Java Persistence with Hibernate.
</para>
</listitem>
<listitem>
Modified: core/trunk/documentation/manual/es-ES/src/main/docbook/modules/tutorial.xml
===================================================================
--- core/trunk/documentation/manual/es-ES/src/main/docbook/modules/tutorial.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/es-ES/src/main/docbook/modules/tutorial.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -585,7 +585,7 @@
Asegúrate de entender el concepto Java de una variable local a una hebra antes
de usar esta ayuda. Una clase <literal>HibernateUtil</literal> más potente puede
encontrarse en <literal>CaveatEmptor</literal>, http://caveatemptor.hibernate.org/,
- así como en el libro "Hibernate in Action". Observa que esta clase no es necesaria
+ así como en el libro "Java Persistence with Hibernate". Observa que esta clase no es necesaria
si despliegas Hibernate en un servidor de aplicaciones J2EE: una <literal>Session</literal>
será automáticamente ligada a la transacción JTA actual, y puedes
buscar la <literal>SessionFactory</literal> a través de JNDI. Si usas JBoss AS,
Modified: core/trunk/documentation/manual/fr-FR/src/main/docbook/master.xml
===================================================================
--- core/trunk/documentation/manual/fr-FR/src/main/docbook/master.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/fr-FR/src/main/docbook/master.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -104,11 +104,11 @@
<listitem>
<para>
Fa�tes de cette documentation de r�f�rence votre principale source d'information.
- Pensez � lire <emphasis>Hibernate in Action</emphasis>
- (http://www.manning.com/bauer) si vous avez besoin de plus d'aide avec le design
+ Pensez � lire <emphasis>Java Persistence with Hibernate</emphasis>
+ (http://www.manning.com/bauer2) si vous avez besoin de plus d'aide avec le design
d'applications ou si vous pr�f�rez un tutoriel pas � pas. Visitez aussi
http://caveatemptor.hibernate.org et t�l�chargez l'application exemple
- pour Hibernate in Action.
+ pour Java Persistence with Hibernate.
</para>
</listitem>
<listitem>
Modified: core/trunk/documentation/manual/ja-JP/src/main/docbook/master.xml
===================================================================
--- core/trunk/documentation/manual/ja-JP/src/main/docbook/master.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/ja-JP/src/main/docbook/master.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -101,10 +101,10 @@
<para>
���̃��t�@�����X�h�L�������g����̏�Ƃ��ė��p���Ă��������B
�A�v���P�[�V�����v�ɂ��Ă̂���Ȃ����i�K�I�ȃ`���[�g���A����T���Ă���Ȃ�A
- <emphasis>Hibernate in Action</emphasis>�ihttp://www.manning.com/bauer�j
+ <emphasis>Java Persistence with Hibernate</emphasis>�ihttp://www.manning.com/bauer2�j
�������߂��܂��B
�܂�http://caveatemptor.hibernate.org����
- Hibernate in Action�̗��̃A�v���P�[�V������_�E�����[�h�ł��܂��B
+ Java Persistence with Hibernate�̗��̃A�v���P�[�V������_�E�����[�h�ł��܂��B
</para>
</listitem>
<listitem>
Modified: core/trunk/documentation/manual/ko-KR/src/main/docbook/master.xml
===================================================================
--- core/trunk/documentation/manual/ko-KR/src/main/docbook/master.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/ko-KR/src/main/docbook/master.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -104,10 +104,10 @@
<para>
당신의 주된 정보의 소스로서 이 참조 문서를 사용하라. 만일 어플리케이션 설계에 대해 더 많은
도움을 필요로 하거나 당신이 단계적인 튜토리얼을 선호한다면
- <emphasis>Hibernate in Action</emphasis>
- (http://www.manning.com/bauer)을 읽는 것을 고려하라.또한
- http://caveatemptor.hibernate.org에 방문하여 Hibernate in
- Action용 예제 어플리케이션을 다운로드 하라.
+ <emphasis>Java Persistence with Hibernate</emphasis>
+ (http://www.manning.com/bauer2)을 읽는 것을 고려하라.또한
+ http://caveatemptor.hibernate.org에 방문하여 Java Persistence
+ with Hibernate용 예제 어플리케이션을 다운로드 하라.
</para>
</listitem>
<listitem>
Modified: core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/tutorial.xml
===================================================================
--- core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/tutorial.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/tutorial.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -521,7 +521,7 @@
<para>
당신이 이 helper를 사용하기 전에 thread-local 변수들에 대한 Java 개념을 확실히 이해하도록 하라.
보다 강력한 <literal>HibernateUtil</literal> helper는 http://caveatemptor.hibernate.org/에
- 있는 <literal>CaveatEmptor</literal> 뿐만 아니라 "Hibernate in Action" 책에서 찾을 수 있다.
+ 있는 <literal>CaveatEmptor</literal> 뿐만 아니라 "Java Persistence with Hibernate" 책에서 찾을 수 있다.
당신이 J2EE 어플리케이션 서버 내에 Hibernate를 배치할 경우에 이 클래스는 필수적이지 않다: 하나의
<literal>Session</literal>은 현재의 JTA 트랜잭션에 자동적으로 바인드 될 것이고 당신은 JNDI를 통해
<literal>SessionFactory</literal>를 룩업할 수 있다. 만일 당신이 JBoss AS를 사용할 경우,
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/master.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/master.xml 2007-07-04 05:55:02 UTC (rev 12721)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/master.xml 2007-07-04 05:59:40 UTC (rev 12722)
@@ -181,11 +181,11 @@
<listitem>
<para>
Use esta documenta��o de referencia como sua fonte primaria de informa��o.
- Considere ler tamb�m o livro <emphasis>Hibernate in Action</emphasis>
- (http://www.manning.com/bauer) caso voc� precise de mais ajuda com o
+ Considere ler tamb�m o livro <emphasis>Java Persistence with Hibernate</emphasis>
+ (http://www.manning.com/bauer2) caso voc� precise de mais ajuda com o
desenvolvimento de aplica��es ou caso prefira um tutorial passo-a-passo.
Tamb�m visite o site http://caveatemptor.hibernate.org e fa�a o download
- da aplica��o de exemplo do Hibernate em A��o.
+ da aplica��o de exemplo do Java Persistence with Hibernate.
</para>
</listitem>
<listitem>
16 years, 10 months
Hibernate SVN: r12721 - in core/trunk/documentation/manual: pt-BR/src/main/docbook/modules and 1 other directories.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 01:55:02 -0400 (Wed, 04 Jul 2007)
New Revision: 12721
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/batch.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/best_practices.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/collection_mapping.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/configuration.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/example_parentchild.xml
core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/best_practices.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/collection_mapping.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/configuration.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/example_parentchild.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/collection_mapping.xml
core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/example_parentchild.xml
core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml
Log:
[HHH-2520] Miscellaneous config doc spelling fixes
and some others.
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -225,7 +225,7 @@
<itemizedlist>
<listitem>
<para>
- <emphasis>Session Management:</emphasis> The Hibernate <literal>Session</literal>'s lifecycle
+ <emphasis>Session Management:</emphasis> The Hibernate <literal>Session</literal>'s life cycle
can be automatically bound to the scope of a JTA transaction. This means you no
longer have to manually open and close the <literal>Session</literal>, this
becomes the job of a JBoss EJB interceptor. You also don't have to worry about
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/batch.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/batch.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/batch.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -111,7 +111,7 @@
Alternatively, Hibernate provides a command-oriented API that may be used for
streaming data to and from the database in the form of detached objects. A
<literal>StatelessSession</literal> has no persistence context associated
- with it and does not provide many of the higher-level lifecycle semantics.
+ with it and does not provide many of the higher-level life cycle semantics.
In particular, a stateless session does not implement a first-level cache nor
interact with any second-level or query cache. It does not implement
transactional write-behind or automatic dirty checking. Operations performed
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/best_practices.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/best_practices.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/best_practices.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -134,7 +134,7 @@
unit-of-work from the point of view of a user. An application transaction might span several
client request/response cycles. It is common to use detached objects to implement application
transactions. An alternative, extremely appropriate in two tiered architecture, is to maintain
- a single open persistence contact (session) for the whole lifecycle of the application transaction
+ a single open persistence contact (session) for the whole life cycle of the application transaction
and simply disconnect from the JDBC connection at the end of each request and reconnect at the
beginning of the subsequent request. Never share a single session across more than one application
transaction, or you will be working with stale data.
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/collection_mapping.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/collection_mapping.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/collection_mapping.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -275,8 +275,8 @@
Collections may contain almost any other Hibernate type, including all basic types,
custom types, components, and of course, references to other entities. This is an
important distinction: an object in a collection might be handled with "value"
- semantics (its lifecycle fully depends on the collection owner) or it might be a
- reference to another entity, with its own lifecycle. In the latter case, only the
+ semantics (its life cycle fully depends on the collection owner) or it might be a
+ reference to another entity, with its own life cycle. In the latter case, only the
"link" between the two objects is considered to be state held by the collection.
</para>
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/configuration.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/configuration.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/configuration.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -167,7 +167,7 @@
<literal>hibernate.connection.driver_class</literal>
</entry>
<entry>
- <emphasis>jdbc driver class</emphasis>
+ <emphasis>JDBC driver class</emphasis>
</entry>
</row>
<row>
@@ -175,7 +175,7 @@
<literal>hibernate.connection.url</literal>
</entry>
<entry>
- <emphasis>jdbc URL</emphasis>
+ <emphasis>JDBC URL</emphasis>
</entry>
</row>
<row>
@@ -253,7 +253,7 @@
<colspec colname="c2" colwidth="1*"/>
<thead>
<row>
- <entry>Propery name</entry>
+ <entry>Property name</entry>
<entry>Purpose</entry>
</row>
</thead>
@@ -321,7 +321,7 @@
<para>
Arbitrary connection properties may be given by prepending
- "<literal>hibernate.connnection</literal>" to the property name. For example, you
+ "<literal>hibernate.connection</literal>" to the property name. For example, you
may specify a <literal>charSet</literal> using <literal>hibernate.connection.charSet</literal>.
</para>
@@ -405,7 +405,7 @@
<literal>hibernate.default_schema</literal>
</entry>
<entry>
- Qualify unqualified tablenames with the given schema/tablespace
+ Qualify unqualified table names with the given schema/tablespace
in generated SQL.
<para>
<emphasis role="strong">eg.</emphasis>
@@ -418,7 +418,7 @@
<literal>hibernate.default_catalog</literal>
</entry>
<entry>
- Qualify unqualified tablenames with the given catalog
+ Qualify unqualified table names with the given catalog
in generated SQL.
<para>
<emphasis role="strong">eg.</emphasis>
@@ -509,7 +509,7 @@
</row>
<row>
<entry>
- <literal>hibernate.use_identifer_rollback</literal>
+ <literal>hibernate.use_identifier_rollback</literal>
</entry>
<entry>
If enabled, generated identifier properties will be
@@ -634,7 +634,7 @@
Enable use of JDBC3 <literal>PreparedStatement.getGeneratedKeys()</literal>
to retrieve natively generated keys after insert. Requires JDBC3+ driver
and JRE1.4+, set to false if your driver has problems with the Hibernate
- identifier generators. By default, tries to determine the driver capabilites
+ identifier generators. By default, tries to determine the driver capabilities
using connection metadata.
<para>
<emphasis role="strong">eg.</emphasis>
@@ -1421,7 +1421,7 @@
a JTA compatible <literal>TransactionManager</literal> and a
<literal>ResourceManager</literal> take care of transaction management (CMT),
esp. distributed transaction handling across several datasources. You may
- of course also demarcate transaction boundaries programatically (BMT) or
+ of course also demarcate transaction boundaries programmatically (BMT) or
you might want to use the optional Hibernate <literal>Transaction</literal>
API for this to keep your code portable.
</para>
@@ -1625,7 +1625,7 @@
<para>
We recommend that you bind the <literal>SessionFactory</literal> to JNDI in
- a managend environment and use a <literal>static</literal> singleton otherwise.
+ a managed environment and use a <literal>static</literal> singleton otherwise.
To shield your application code from these details, we also recommend to hide the
actual lookup code for a <literal>SessionFactory</literal> in a helper class,
such as <literal>HibernateUtil.getSessionFactory()</literal>. Note that such a
@@ -1649,7 +1649,7 @@
will be set to automatically flush before the transaction completes, close
after the transaction completes, and aggressively release JDBC connections
after each statement. This allows the <literal>Session</literal>s to
- be managed by the lifecycle of the JTA transaction to which it is associated,
+ be managed by the life cycle of the JTA transaction to which it is associated,
keeping user code clean of such management concerns. Your code can either use
JTA programmatically through <literal>UserTransaction</literal>, or (recommended
for portable code) use the Hibernate <literal>Transaction</literal> API to set
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/example_parentchild.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/example_parentchild.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/example_parentchild.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -52,7 +52,7 @@
Instead, the default behaviour is that adding an entity to a collection merely creates a link between
the two entities, while removing it removes the link. This is very appropriate for all sorts of cases.
Where it is not appropriate at all is the case of a parent / child relationship, where the life of the
- child is bound to the lifecycle of the parent.
+ child is bound to the life cycle of the parent.
</para>
</sect1>
@@ -171,7 +171,7 @@
</sect1>
<sect1 id="example-parentchild-cascades">
- <title>Cascading lifecycle</title>
+ <title>Cascading life cycle</title>
<para>
The explicit call to <literal>save()</literal> is still annoying. We will address this by
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -1059,7 +1059,7 @@
<para>
If the children in a parent/child relationship would be value typed (e.g. a collection
- of addresses or strings), their lifecycle would depend on the parent and no
+ of addresses or strings), their life cycle would depend on the parent and no
further action would be required for convenient "cascading" of state changes.
When the parent is saved, the value-typed child objects are saved as
well, when the parent is deleted, the children will be deleted, etc. This
@@ -1071,7 +1071,7 @@
<para>
Now consider the same scenario with parent and child objects being entities,
not value-types (e.g. categories and items, or parent and child cats). Entities
- have their own lifecycle, support shared references (so removing an entity from
+ have their own life cycle, support shared references (so removing an entity from
the collection does not mean it can be deleted), and there is by default no
cascading of state from one entity to any other associated entities. Hibernate
does not implement <emphasis>persistence by reachability</emphasis> by default.
@@ -1123,7 +1123,7 @@
<listitem>
<para>
If the child object's lifespan is bounded by the lifespan of the of the parent
- object make it a <emphasis>lifecycle object</emphasis> by specifying
+ object make it a <emphasis>life cycle object</emphasis> by specifying
<literal>cascade="all,delete-orphan"</literal>.
</para>
</listitem>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/best_practices.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/best_practices.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/best_practices.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -132,11 +132,11 @@
<listitem>
<para>
Database Transactions have to be as short as possible for best scalability. However, it is often
- neccessary to implement long running <emphasis>application transactions</emphasis>, a single
+ necessary to implement long running <emphasis>application transactions</emphasis>, a single
unit-of-work from the point of view of a user. An application transaction might span several
client request/response cycles. It is common to use detached objects to implement application
transactions. An alternative, extremely appropriate in two tiered architecture, is to maintain
- a single open persistence contact (session) for the whole lifecycle of the application transaction
+ a single open persistence contact (session) for the whole life cycle of the application transaction
and simply disconnect from the JDBC connection at the end of each request and reconnect at the
beginning of the subsequent request. Never share a single session across more than one application
transaction, or you will be working with stale data.
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/collection_mapping.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/collection_mapping.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/collection_mapping.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -275,8 +275,8 @@
Collections may contain almost any other Hibernate type, including all basic types,
custom types, components, and of course, references to other entities. This is an
important distinction: an object in a collection might be handled with "value"
- semantics (its lifecycle fully depends on the collection owner) or it might be a
- reference to another entity, with its own lifecycle. In the latter case, only the
+ semantics (its life cycle fully depends on the collection owner) or it might be a
+ reference to another entity, with its own life cycle. In the latter case, only the
"link" between the two objects is considered to be state held by the collection.
</para>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/configuration.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/configuration.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/configuration.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -1700,7 +1700,7 @@
will be set to automatically flush before the transaction completes, close
after the transaction completes, and aggressively release JDBC connections
after each statement. This allows the <literal>Session</literal>s to
- be managed by the lifecycle of the JTA transaction to which it is associated,
+ be managed by the life cycle of the JTA transaction to which it is associated,
keeping user code clean of such management concerns. Your code can either use
JTA programmatically through <literal>UserTransaction</literal>, or (recommended
for portable code) use the Hibernate <literal>Transaction</literal> API to set
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/example_parentchild.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/example_parentchild.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/example_parentchild.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -52,7 +52,7 @@
Instead, the default behaviour is that adding an entity to a collection merely creates a link between
the two entities, while removing it removes the link. This is very appropriate for all sorts of cases.
Where it is not appropriate at all is the case of a parent / child relationship, where the life of the
- child is bound to the lifecycle of the parent.
+ child is bound to the life cycle of the parent.
</para>
</sect1>
@@ -171,7 +171,7 @@
</sect1>
<sect1 id="example-parentchild-cascades">
- <title>Cascading lifecycle</title>
+ <title>Cascading life cycle</title>
<para>
The explicit call to <literal>save()</literal> is still annoying. We will address this by
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -1067,7 +1067,7 @@
<para>
If the children in a parent/child relationship would be value typed (e.g. a collection
- of addresses or strings), their lifecycle would depend on the parent and no
+ of addresses or strings), their life cycle would depend on the parent and no
further action would be required for convenient "cascading" of state changes.
When the parent is saved, the value-typed child objects are saved as
well, when the parent is deleted, the children will be deleted, etc. This
@@ -1079,7 +1079,7 @@
<para>
Now consider the same scenario with parent and child objects being entities,
not value-types (e.g. categories and items, or parent and child cats). Entities
- have their own lifecycle, support shared references (so removing an entity from
+ have their own life cycle, support shared references (so removing an entity from
the collection does not mean it can be deleted), and there is by default no
cascading of state from one entity to any other associated entities. Hibernate
does not implement <emphasis>persistence by reachability</emphasis> by default.
@@ -1131,7 +1131,7 @@
<listitem>
<para>
If the child object's lifespan is bounded by the lifespan of the of the parent
- object make it a <emphasis>lifecycle object</emphasis> by specifying
+ object make it a <emphasis>life cycle object</emphasis> by specifying
<literal>cascade="all,delete-orphan"</literal>.
</para>
</listitem>
Modified: core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/collection_mapping.xml
===================================================================
--- core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/collection_mapping.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/collection_mapping.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -478,7 +478,7 @@
</bag>]]></programlisting>
<para>
- 一个实体数组,在这个案例中是一个多对多的关联(注意这里的实体是自动管理生命周期的对象（lifecycle objects）,<literal>cascade="all"</literal>):
+ 一个实体数组,在这个案例中是一个多对多的关联(注意这里的实体是自动管理生命周期的对象（life cycle objects）,<literal>cascade="all"</literal>):
</para>
Modified: core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/example_parentchild.xml
===================================================================
--- core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/example_parentchild.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/example_parentchild.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -137,7 +137,7 @@
</sect1>
<sect1 id="example-parentchild-cascades">
- <title>级联生命周期（Cascading lifecycle）</title>
+ <title>级联生命周期（Cascading life cycle）</title>
<para>
需要显式调用<literal>save()</literal>仍然很麻烦，我们可以用级联来解决这个问题。
</para>
Modified: core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml 2007-07-04 05:33:48 UTC (rev 12720)
+++ core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml 2007-07-04 05:55:02 UTC (rev 12721)
@@ -1019,7 +1019,7 @@
</listitem>
<listitem>
<para>
- 如果子对象的寿命限定在父亲对象的寿命之内，可通过指定<literal>cascade="all,delete-orphan"</literal>将其变为<emphasis>自动生命周期管理的对象(lifecycle object)</emphasis>。
+ 如果子对象的寿命限定在父亲对象的寿命之内，可通过指定<literal>cascade="all,delete-orphan"</literal>将其变为<emphasis>自动生命周期管理的对象(life cycle object)</emphasis>。
</para>
</listitem>
<listitem>
16 years, 10 months
Hibernate SVN: r12720 - core/trunk/code/core/src/main/javadoc.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 01:33:48 -0400 (Wed, 04 Jul 2007)
New Revision: 12720
Modified:
core/trunk/code/core/src/main/javadoc/package.html
Log:
[HHH-2568] Hibernate javadoc overview refering wrong classes and packages
Modified: core/trunk/code/core/src/main/javadoc/package.html
===================================================================
--- core/trunk/code/core/src/main/javadoc/package.html 2007-07-04 05:24:14 UTC (rev 12719)
+++ core/trunk/code/core/src/main/javadoc/package.html 2007-07-04 05:33:48 UTC (rev 12720)
@@ -11,9 +11,9 @@
<li><tt>org.hibernate.Criteria</tt></li>
<li><tt>org.hibernate.ScrollableResults</tt></li>
<li><tt>org.hibernate.cfg.Configuration</tt></li>
-<li><tt>org.hibernate.expression.Expression</tt></li>
-<li><tt>org.hibernate.expression.Order</tt></li>
-<li><tt>org.hibernate.expression.Example</tt></li>
+<li><tt>org.hibernate.criterion.Restrictions</tt></li>
+<li><tt>org.hibernate.criterion.Order</tt></li>
+<li><tt>org.hibernate.criterion.Example</tt></li>
These interfaces are fully intended to be exposed to application code.<br>
<br>
The <b>Extension API</b> is intended to be used by application programmers
@@ -33,7 +33,7 @@
@see org.hibernate.Criteria
@see org.hibernate.ScrollableResults
@see org.hibernate.cfg.Configuration
-@see org.hibernate.expression.Expression
-@see org.hibernate.expression.Order
-@see org.hibernate.expression.Example
+@see org.hibernate.criterion.Restrictions
+@see org.hibernate.criterion.Order
+@see org.hibernate.criterion.Example
</body>
16 years, 10 months
Hibernate SVN: r12719 - in core/trunk/documentation/manual: pt-BR/src/main/docbook/modules and 1 other directory.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 01:24:14 -0400 (Wed, 04 Jul 2007)
New Revision: 12719
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/basic_mapping.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml
Log:
[HHH-2334] Documentation error in section 5.1.3
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml 2007-07-04 05:12:00 UTC (rev 12718)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml 2007-07-04 05:24:14 UTC (rev 12719)
@@ -474,7 +474,7 @@
The optional <literal>proxy</literal> attribute enables lazy initialization of persistent
instances of the class. Hibernate will initially return CGLIB proxies which implement
the named interface. The actual persistent object will be loaded when a method of the
- proxy is invoked. See "Proxies for Lazy Initialization" below.
+ proxy is invoked. See "Initializing collections and proxies" below.
</para>
<para><emphasis>Implicit</emphasis> polymorphism means that instances of the class will be returned
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/basic_mapping.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/basic_mapping.xml 2007-07-04 05:12:00 UTC (rev 12718)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/basic_mapping.xml 2007-07-04 05:24:14 UTC (rev 12719)
@@ -488,7 +488,7 @@
O atributo opcional <literal>proxy</literal> habilita a inicialização tardia das
instâncias persistentes da classe. O Hibernate irá retornar CGLIB proxies como implementado
na interface nomeada. O objeto persistente atual será carregado quando um método do proxy
- for invocado. Veja "Proxies para Inicialização Lazy" abaixo.
+ for invocado. Veja "Inicializando coleções e proxies" abaixo.
</para>
<para>Polimorfismo <emphasis>implícito</emphasis> significa que instâncias de uma classe
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml 2007-07-04 05:12:00 UTC (rev 12718)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/performance.xml 2007-07-04 05:24:14 UTC (rev 12719)
@@ -109,7 +109,7 @@
</para>
<sect2 id="performance-fetching-lazy">
- <title>Trabalhando com associações preguiçosas (lazy)</title>
+ <title>Inicializando coleções e proxies</title>
<para>
Por padrão, o Hibernate3 usa busca preguiçosa para coleções e busca preguiçosa
16 years, 10 months
Hibernate SVN: r12718 - in core/trunk/documentation/manual: pt-BR/src/main/docbook/modules and 1 other directory.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 01:12:00 -0400 (Wed, 04 Jul 2007)
New Revision: 12718
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial1.xml
Log:
[HHH-2418] Refer HSQL DB website in chapter 1.2.3
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml 2007-07-04 05:02:44 UTC (rev 12717)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/tutorial.xml 2007-07-04 05:12:00 UTC (rev 12718)
@@ -323,7 +323,7 @@
<para>
We now have a persistent class and its mapping file in place. It is time to configure
Hibernate. Before we do this, we will need a database. HSQL DB, a java-based SQL DBMS,
- can be downloaded from the HSQL DB website. Actually, you only need the <literal>hsqldb.jar</literal>
+ can be downloaded from the HSQL DB website(http://hsqldb.org/). Actually, you only need the <literal>hsqldb.jar</literal>
from this download. Place this file in the <literal>lib/</literal> directory of the
development folder.
</para>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial.xml 2007-07-04 05:02:44 UTC (rev 12717)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial.xml 2007-07-04 05:12:00 UTC (rev 12718)
@@ -317,7 +317,7 @@
<para>
Agora nós temos uma classe persistente e este arquivo de mapeamento no lugar.
Está na hora de configurar o Hibernate. Antes de fazermos isso, iremos precisar de uma base de dados.
- O HSQL DB, um SQL DBMS feito em java, pode ser baixado através do site do HSQL DB.
+ O HSQL DB, um SQL DBMS feito em java, pode ser baixado através do site do HSQL DB(http://hsqldb.org/).
Atualmente, você só precisa baixar o <literal>hsqldb.jar</literal>.
Coloque este arquivo no diretório da pasta de desenvolvimento <literal>lib/</literal>.
</para>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial1.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial1.xml 2007-07-04 05:02:44 UTC (rev 12717)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/tutorial1.xml 2007-07-04 05:12:00 UTC (rev 12718)
@@ -317,7 +317,7 @@
<para>
Agora nós temos uma classe persistente e este arquivo de mapeamento no lugar.
Está na hora de configurar o Hibernate. Antes de fazermos isso, iremos precisar de uma base de dados.
- O HSQL DB, um SQL DBMS feito em java, pode ser baixado através do site do HSQL DB.
+ O HSQL DB, um SQL DBMS feito em java, pode ser baixado através do site do HSQL DB(http://hsqldb.org/).
Atualmente, você só precisa baixar o <literal>hsqldb.jar</literal>.
Coloque este arquivo no diretório da pasta de desenvolvimento <literal>lib/</literal>.
</para>
16 years, 10 months
Hibernate SVN: r12717 - in core/trunk/documentation/manual: es-ES/src/main/docbook/modules and 5 other directories.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 01:02:44 -0400 (Wed, 04 Jul 2007)
New Revision: 12717
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/es-ES/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml
core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml
Log:
[HHH-2550] Update API Class in 10.4.3. Criteria queries
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -550,7 +550,7 @@
</para>
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
Modified: core/trunk/documentation/manual/es-ES/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/es-ES/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/es-ES/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -542,7 +542,7 @@
</para>
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
Modified: core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/fr-FR/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -536,7 +536,7 @@
</para>
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
Modified: core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -517,7 +517,7 @@
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
Modified: core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -501,7 +501,7 @@
</para>
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -558,7 +558,7 @@
</para>
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
Modified: core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml
===================================================================
--- core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml 2007-07-04 04:58:58 UTC (rev 12716)
+++ core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/session_api.xml 2007-07-04 05:02:44 UTC (rev 12717)
@@ -496,7 +496,7 @@
</para>
<programlisting><![CDATA[Criteria crit = session.createCriteria(Cat.class);
-crit.add( Expression.eq( "color", eg.Color.BLACK ) );
+crit.add( Restrictions.eq( "color", eg.Color.BLACK ) );
crit.setMaxResults(10);
List cats = crit.list();]]></programlisting>
16 years, 10 months
Hibernate SVN: r12716 - in core/trunk/documentation/manual: pt-BR/src/main/docbook/modules and 1 other directory.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 00:58:58 -0400 (Wed, 04 Jul 2007)
New Revision: 12716
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/architecture.xml
Log:
[HHH-2420] Error in 2.5. Contextual Sessions
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml 2007-07-04 04:55:21 UTC (rev 12715)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/architecture.xml 2007-07-04 04:58:58 UTC (rev 12716)
@@ -345,7 +345,7 @@
but a <literal>org.hibernate.transaction.TransactionManagerLookup</literal> is configured,
Hibernate will use the <literal>org.hibernate.context.JTASessionContext</literal>.
Typically, the value of this parameter would just name the implementation class to
- use; for the three out-of-the-box implementations, however, there are two corresponding
+ use; for the three out-of-the-box implementations, however, there are three corresponding
short names, "jta", "thread", and "managed".
</para>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/architecture.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/architecture.xml 2007-07-04 04:55:21 UTC (rev 12715)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/architecture.xml 2007-07-04 04:58:58 UTC (rev 12716)
@@ -350,7 +350,7 @@
não é determinado mas um <literal>org.hibernate.transaction.TransactionManagerLookup</literal>
é configurado, Hibernate usará o <literal>org.hibernate.context.JTASessionContext</literal>.
Tipicamente, o valor deste parâmetro nomearia apenas a classe de implementação para usar;
- para as duas implementações out-of-the-box, entretanto, há dois pequenos nomes correspondentes,
+ para as duas implementações out-of-the-box, entretanto, há três pequenos nomes correspondentes,
"jta", "thread", and "managed".
</para>
16 years, 10 months
Hibernate SVN: r12715 - in core/trunk/documentation/manual: ja-JP/src/main/docbook/modules and 3 other directories.
by hibernate-commits＠lists.jboss.org
Author: d.plentz
Date: 2007-07-04 00:55:21 -0400 (Wed, 04 Jul 2007)
New Revision: 12715
Modified:
core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml
core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml
core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml
core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml
core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml
Log:
[HHH-2567] Update reference to use FlushMode.MANUAL
Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml
===================================================================
--- core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714)
+++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715)
@@ -802,7 +802,7 @@
force a version check on data you aren't updating, you may call <literal>Session.lock()</literal>
with <literal>LockMode.READ</literal> on any objects that might have been updated by another
transaction. You don't need to lock any data that you <emphasis>are</emphasis> updating.
- Usually you would set <literal>FlushMode.NEVER</literal> on an extended <literal>Session</literal>,
+ Usually you would set <literal>FlushMode.MANUAL</literal> on an extended <literal>Session</literal>,
so that only the last database transaction cycle is allowed to actually persist all
modifications made in this conversation. Hence, only this last database transaction
would include the <literal>flush()</literal> operation, and then also
Modified: core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml
===================================================================
--- core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714)
+++ core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715)
@@ -937,7 +937,7 @@
��Ăяo�����Ƃ��ł��܂��B
�X�V���� <emphasis>����</emphasis> �f�[�^���b�N����K�v�͂���܂���B
- �ʏ�A�g�� <literal>Session</literal> �� <literal>FlushMode.NEVER</literal>
+ �ʏ�A�g�� <literal>Session</literal> �� <literal>FlushMode.MANUAL</literal>
��Z�b�g���܂��B
�Ō�̃f�[�^�x�[�X�g�����U�N�V�����̎����ł̂݁A
�Θb�̒��ŕύX���ꂽ���ׂĂ���ۂɉi���������邽�߂ł��B
Modified: core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml
===================================================================
--- core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714)
+++ core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715)
@@ -721,7 +721,7 @@
또 다른 트랜잭션에 의해 업데이트되었을 수도 있는 임의의 객체들에 대해 <literal>LockMode.READ</literal>로서
<literal>Session.lock()</literal>을 호출할 수도 있다. 당신은 당신이 업데이트 중인 임의의 데이터를 잠금할 필요가 없다.
대개 당신은 마지막 데이터베이스 트랜잭션 주기만이 이 대화 내에서 행해진 모든 변경들을 실제로 영속화시키는 것이 허용되도록 하기 위해,
- 하나의 확장된 <literal>Session</literal>에 대해 <literal>FlushMode.NEVER</literal>를 설정할 것이다.
+ 하나의 확장된 <literal>Session</literal>에 대해 <literal>FlushMode.MANUAL</literal>를 설정할 것이다.
그러므로 오직 이 마지막 데이터베이스 트랜잭션 만이 <literal>flush()</literal> 오퍼레이션을 포함할 것이고, 또한
대화를 종료시키기 위해 세션을 <literal>close()</literal>할 것이다.
</para>
Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml
===================================================================
--- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714)
+++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715)
@@ -829,7 +829,7 @@
forçar uma checagem de versão em dados que você não está atualizando, você pode chamar
<literal>Session.lock()</literal> com o <literal>LockMode.READ</literal> em todos os objetos
que possam ter sido atualizados por uma outra transação. Você não necessita bloquear nenhum
- dado para atualizar. Geralmente você configuraria <literal>FlushMode.NEVER</literal> em uma
+ dado para atualizar. Geralmente você configuraria <literal>FlushMode.MANUAL</literal> em uma
<literal>Session</literal> estendida, de modo que somente o último ciclo da transação tenha
permissão de persistir todas as modificações feitas nesta conversação. Disso, somente esta última
transação incluiria a operação <literal>flush()</literal> e então chamar também <literal>close()</literal>
Modified: core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml
===================================================================
--- core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714)
+++ core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715)
@@ -618,7 +618,7 @@
session.close(); // Only for last transaction in conversation]]></programlisting>
<para>
- <literal>foo</literal>对象知道它是在哪个<literal>Session</literal>中被装入的。在一个旧session中开启一个新的数据库事务，会导致session获取一个新的连接，并恢复session的功能。将数据库事务提交，使得session从JDBC连接断开，并将此连接交还给连接池。在重新连接之后，要强制对你没有更新的数据进行一次版本检查，你可以对所有可能被其他事务修改过的对象，使用参数<literal>LockMode.READ</literal>来调用<literal>Session.lock()</literal>。你不用lock任何你<emphasis>正在</emphasis>更新的数据。一般你会在扩展的<literal>Session</literal>上设置<literal>FlushMode.NEVER</literal>，因此只有最后一个数据库事务循环才会真正的吧整个对话中发生的修改发送到数据库。因此，只有这最后一次数据库事务才会包含<literal>flush()</literal>操作，然后在整个对话结束后，还要<literal!
>close()</literal>这个session。
+ <literal>foo</literal>对象知道它是在哪个<literal>Session</literal>中被装入的。在一个旧session中开启一个新的数据库事务，会导致session获取一个新的连接，并恢复session的功能。将数据库事务提交，使得session从JDBC连接断开，并将此连接交还给连接池。在重新连接之后，要强制对你没有更新的数据进行一次版本检查，你可以对所有可能被其他事务修改过的对象，使用参数<literal>LockMode.READ</literal>来调用<literal>Session.lock()</literal>。你不用lock任何你<emphasis>正在</emphasis>更新的数据。一般你会在扩展的<literal>Session</literal>上设置<literal>FlushMode.MANUAL</literal>，因此只有最后一个数据库事务循环才会真正的吧整个对话中发生的修改发送到数据库。因此，只有这最后一次数据库事务才会包含<literal>flush()</literal>操作，然后在整个对话结束后，还要<litera!
l>close()</literal>这个session。
</para>
<para>
16 years, 10 months