mirror of https://github.com/apache/openjpa.git
OPENJPA-1673: Update docs for MetaDataRepository.
git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@946726 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
1c01e8da2a
commit
4a1ab58598
|
@ -126,23 +126,18 @@ scanned for annotated JPA entities.
|
|||
<itemizedlist>
|
||||
<listitem><para>
|
||||
<literal>Preload</literal>: A boolean property. If true, OpenJPA will eagerly load the repository on
|
||||
EntityManagerFactory creation. As a result, all Entity classes will be eagerly loaded by the JVM. If
|
||||
false, the repository will be lazily loaded as Entity classes are loaded by the JVM. The default value
|
||||
is false.
|
||||
EntityManagerFactory creation. As a result, all Entity classes will be eagerly loaded by the JVM.
|
||||
Once MetaData preloading completes, all locking is removed from the MetaDataRepository and this will
|
||||
result in a much more scalable repository. If false, the repository will be lazily loaded as Entity
|
||||
classes are loaded by the JVM. The default value is false.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>
|
||||
<literal>NoLock</literal>: If true, the repository will be treated as a read only data structure and
|
||||
minimal locking will be imposed on users. Preload must be set to true for OpenJPA to honor setting
|
||||
NoLock to true. The default value is false.
|
||||
</para>
|
||||
</listitem>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<title>Metadata Repository</title>
|
||||
<example id="ref_guide_meta_repo">
|
||||
<programlisting>
|
||||
<property name="openjpa.MetaDataRepository" value="Preload=true,NoLock=true"/>
|
||||
<property name="openjpa.MetaDataRepository" value="Preload=true"/>
|
||||
</programlisting>
|
||||
</example>
|
||||
</section>
|
||||
|
|
|
@ -606,6 +606,21 @@ scalability problems. You can disable this protective behavior by setting the
|
|||
linkend="ref_guide_runtime_broker_finalization"/> for details.
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry colname="name">
|
||||
<emphasis role="bold">
|
||||
Preload MetaDataRepository
|
||||
</emphasis>
|
||||
<para>
|
||||
<emphasis>scalability</emphasis>
|
||||
</para>
|
||||
</entry>
|
||||
<entry colname="desc">
|
||||
By default, the MetaDataRepository is lazily loaded which means that fair amounts of locking
|
||||
is used to ensure that metadata is processed properly. Enabling preloading allows OpenJPA to
|
||||
load metadata upfront and remove locking. See <xref linkend="ref_guide_meta_repository"/> for details.
|
||||
</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
|
|
@ -354,7 +354,7 @@ use detached state managers, as determined by the settings above.
|
|||
DetachState setting.</emphasis> Detach all fields and relations as described by the loaded
|
||||
property when an explicit detach is requested or when a
|
||||
single Entity is being detached as part of serialization. When the entire
|
||||
persistence context is being auto-detached(@See openjpa.AutoDetach),
|
||||
persistence context is being auto-detached ( <literal>openjpa.AutoDetach</literal> ),
|
||||
the minimal amount of work will be completed to disassociate all Entities from
|
||||
the persistence context. <emphasis role="bold">It is highly recommended that all Entities have a
|
||||
@Version field when using this property</emphasis>. In addition, care needs to be taken
|
||||
|
|
Loading…
Reference in New Issue