Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_deploy.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_deploy.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_deploy.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_deploy.xml Thu Jun 28 09:32:10 2018 @@ -58,7 +58,7 @@ The JPA Overview describes the <classnam <classname>Persistence</classname> to add additional <classname> EntityManagerFactory</classname> creation methods. The <classname> org.apache.openjpa.persistence.OpenJPAPersistence</classname> class -<ulink url="../javadoc/org/apache/openjpa/persistence/OpenJPAPersistence.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/OpenJPAPersistence.html"> Javadoc</ulink> details these extensions. </para> <para> @@ -164,7 +164,7 @@ manager for an unrecognized or non-stand accomplished through the <link linkend="openjpa.ManagedRuntime"><literal> openjpa.ManagedRuntime</literal></link> configuration property. This property describes an -<ulink url="../javadoc/org/apache/openjpa/ee/ManagedRuntime.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/ee/ManagedRuntime.html"><classname> org.apache.openjpa.ee.ManagedRuntime</classname></ulink> implementation to use for transaction manager discovery. You can specify your own implementation, or use one of the built-ins: @@ -173,7 +173,7 @@ or use one of the built-ins: <listitem> <para> <literal>auto</literal>: This is the default. It is an alias for the -<ulink url="../javadoc/org/apache/openjpa/ee/AutomaticManagedRuntime.html"> +<ulink url="../../apidocs/org/apache/openjpa/ee/AutomaticManagedRuntime.html"> <classname>org.apache.openjpa.ee.AutomaticManagedRuntime</classname></ulink> class. This managed runtime is able to automatically integrate with several common application servers. @@ -182,7 +182,7 @@ common application servers. <listitem> <para> <literal>invocation</literal>: An alias for the -<ulink url="../javadoc/org/apache/openjpa/ee/InvocationManagedRuntime.html"> +<ulink url="../../apidocs/org/apache/openjpa/ee/InvocationManagedRuntime.html"> <classname>org.apache.openjpa.ee.InvocationManagedRuntime</classname></ulink> class. You can configure this runtime to invoke any static method in order to obtain the appserver's transaction manager. @@ -191,7 +191,7 @@ method in order to obtain the appserver' <listitem> <para> <literal>jndi</literal>: An alias for the -<ulink url="../javadoc/org/apache/openjpa/ee/JNDIManagedRuntime.html"> +<ulink url="../../apidocs/org/apache/openjpa/ee/JNDIManagedRuntime.html"> <classname>org.apache.openjpa.ee.JNDIManagedRuntime</classname></ulink> class. You can configure this runtime to look up the transaction manager at any JNDI location.
Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_encryption.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_encryption.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_encryption.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_encryption.xml Thu Jun 28 09:32:10 2018 @@ -25,7 +25,7 @@ OpenJPA provides an interface for a provider to implement connection password encryption. Whenever a connection password is needed, the <methodname>decrypt(String)</methodname> method will be invoked. See - <ulink url="../javadoc/org/apache/openjpa/lib/encryption/EncryptionProvider.html"> + <ulink url="../../apidocs/org/apache/openjpa/lib/encryption/EncryptionProvider.html"> <classname>org.apache.openjpa.lib.encryption.EncryptionProvider</classname> </ulink> for the detailed Javadoc. </para> Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml Thu Jun 28 09:32:10 2018 @@ -114,9 +114,9 @@ <para> OpenJPA includes built-in support for a JMX Platform MBean provider, but a custom instrumentation providers can be created by implementing the - <ulink url="../javadoc/org/apache/openjpa/lib/instrumentation/InstrumentationProvider.html"> + <ulink url="../../apidocs/org/apache/openjpa/lib/instrumentation/InstrumentationProvider.html"> <classname>InstrumentationProvider</classname></ulink> interface or more simply by extending - <ulink url="../javadoc/org/apache/openjpa/lib/instrumentation/AbstractInstrumentationProvider.html"> + <ulink url="../../apidocs/org/apache/openjpa/lib/instrumentation/AbstractInstrumentationProvider.html"> <classname>AbstractInstrumentationProvider</classname></ulink>. To use the custom instrumentation provider, include the class in your classpath and specify the class name as the base value on the <link linkend="openjpa.Instrumentation"><literal>openjpa.Instrumentation</literal></link> configuration property. @@ -124,12 +124,12 @@ <para> OpenJPA includes instruments for various caches, but you can also create your own instruments. To create a custom instrument you need to implement the - <ulink url="../javadoc/org/apache/openjpa/lib/instrumentation/Instrument.html"> + <ulink url="../../apidocs/org/apache/openjpa/lib/instrumentation/Instrument.html"> <classname>Instrument</classname></ulink> interface or more simply extend - <ulink url="../javadoc/org/apache/openjpa/lib/instrumentation/AbstractInstrument.html"> + <ulink url="../../apidocs/org/apache/openjpa/lib/instrumentation/AbstractInstrument.html"> <classname>AbstractInstrument</classname></ulink>. If you are building a Platform MBean JMX-based instrument this effort can be simplified by extending - <ulink url="../javadoc/org/apache/openjpa/instrumentation/jmx/JMXInstrument.html"> + <ulink url="../../apidocs/org/apache/openjpa/instrumentation/jmx/JMXInstrument.html"> <classname>JMXInstrument</classname></ulink>. If you create your own custom provider, class name aliases can be registered within the provider to simplify configuration. For example, the instrument <classname>com.my.app.MySQLInstrument</classname> could be aliased as Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_integration.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_integration.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_integration.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_integration.xml Thu Jun 28 09:32:10 2018 @@ -98,7 +98,7 @@ environment. All OpenJPA tasks accept a nested <literal>config</literal> element, which defines the configuration environment in which the specified task will run. The attributes for the <literal>config</literal> tag are defined by the -<ulink url="../javadoc/org/apache/openjpa/jdbc/conf/JDBCConfiguration.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/conf/JDBCConfiguration.html"> <classname>JDBCConfiguration</classname></ulink> bean methods. Note that excluding the <literal>config</literal> element will cause the Ant task to use the default system configuration mechanism, such as the configuration defined in Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_logging.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_logging.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_logging.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_logging.xml Thu Jun 28 09:32:10 2018 @@ -549,7 +549,7 @@ logging to a graphical component for GUI </para> <para> A custom logging framework must include an implementation of the -<ulink url="../javadoc/org/apache/openjpa/lib/log/LogFactory.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/lib/log/LogFactory.html"><classname> org.apache.openjpa.lib.log.LogFactory</classname></ulink> interface. We present a custom <classname>LogFactory</classname> below. </para> Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_mapping.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_mapping.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_mapping.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_mapping.xml Thu Jun 28 09:32:10 2018 @@ -66,7 +66,7 @@ their corresponding database schema from forward mapping through the <emphasis>mapping tool</emphasis>. The next section presents several common mapping tool use cases. You can invoke the tool through its Java class, -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/MappingTool"><classname> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/MappingTool"><classname> org.apache.openjpa.jdbc.meta.MappingTool</classname></ulink>. </para> <note> @@ -502,7 +502,7 @@ proper relations between the persistent Run the reverse mapping tool on the finished schema file. If you do not supply the schema file to reverse map, the tool will run directly against the schema in the database. The tool can be run via its Java class, -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/ReverseMappingTool"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/ReverseMappingTool"> <classname>org.apache.openjpa.jdbc.meta.ReverseMappingTool</classname></ulink>. </para> <example id="ref_guide_pc_reverse_reversemappingtool"> @@ -689,11 +689,11 @@ OpenJPA is examining. <para> <literal>-customizerClass/-cc <class name></literal>: The full class name of a -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/ReverseCustomizer.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/ReverseCustomizer.html"> <classname>org.apache.openjpa.jdbc.meta.ReverseCustomizer</classname></ulink> customization plugin. If you do not specify a reverse customizer of your own, the system defaults to a -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/PropertiesReverseCustomizer.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/PropertiesReverseCustomizer.html"> <classname>PropertiesReverseCustomizer</classname></ulink>. This customizer allows you to specify simple customization options in the properties file given with the <literal>-customizerProperties</literal> flag below. We present the @@ -753,7 +753,7 @@ Your persistent classes are now ready to <para> The <classname>org.apache.openjpa.jdbc.meta.ReverseCustomizer</classname> plugin interface allows you to customize the reverse mapping process. See the class -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/ReverseCustomizer.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/ReverseCustomizer.html"> Javadoc</ulink> for details on the hooks that this interface provides. Specify the concrete plugin implementation to use with the <literal> -customizerClass/-cc</literal> command-line flag, described in the preceding @@ -761,7 +761,7 @@ section. </para> <para> By default, the reverse mapping tool uses a -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/PropertiesReverseCustomizer.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/PropertiesReverseCustomizer.html"> <classname>org.apache.openjpa.jdbc.meta.PropertiesReverseCustomizer</classname> </ulink>. This customizer allows you to perform relatively simple customizations through the properties file named with the <literal> @@ -996,7 +996,7 @@ database's tools to bring the schema up- The previous sections showed how to use the mapping tool to generate default mappings. But how does the mapping tool know what mappings to generate? The answer lies in the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/MappingDefaults.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/MappingDefaults.html"> <classname>org.apache.openjpa.jdbc.meta.MappingDefaults</classname></ulink> interface. OpenJPA uses an instance of this interface to decide how to name tables and columns, where to put foreign keys, and generally how to create a @@ -1025,7 +1025,7 @@ OpenJPA includes the following standard <para> <literal>jpa</literal>: Provides defaults in compliance with the JPA standard. This is an alias for the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/PersistenceMappingDefaults.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/PersistenceMappingDefaults.html"> <classname>org.apache.openjpa.persistence.jdbc.PersistenceMappingDefaults </classname></ulink> class. This class extends the <classname> MappingDefaultsImpl</classname> class described below, so it has all the same @@ -1045,7 +1045,7 @@ compatibility with older OpenJPA version <listitem> <para> <literal>default</literal>: This is an alias for the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/MappingDefaultsImpl.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/MappingDefaultsImpl.html"> <classname>org.apache.openjpa.jdbc.meta.MappingDefaultsImpl</classname></ulink> class. This default implementation is highly configurable. It has the following properties: @@ -1079,7 +1079,7 @@ classes. You can specify a built-in stra You can also use OpenJPA's plugin format (see <xref linkend="ref_guide_conf_plugins"/>) to pass arguments to the strategy instance. See the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> <literal>org.apache.openjpa.jdbc.meta.strats</literal></ulink> package for available strategies. </para> @@ -1093,7 +1093,7 @@ You can also use OpenJPA's plugin format <xref linkend="ref_guide_conf_plugins"/>) to pass arguments to the strategy instance. Common strategies are <literal>vertical</literal> and <literal>flat</literal>, the default. See the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> <literal>org.apache.openjpa.jdbc.meta.strats</literal></ulink> package for all available strategies. </para> @@ -1108,7 +1108,7 @@ version strategy</link>. You can also us strategy instance. Common strategies are <literal>none</literal>, <literal> state-comparison</literal>, <literal> timestamp</literal>, and <literal> version-number</literal>, the default. See the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> <literal>org.apache.openjpa.jdbc.meta.strats</literal></ulink> package for all available strategies. </para> @@ -1125,7 +1125,7 @@ strategy instance. Common strategies are class without subclasses, <literal>none</literal> to use joins to subclass tables rather than a discriminator column, and <literal> class-name</literal>, the default. See the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/strats/package-summary.html"> <literal>org.apache.openjpa.jdbc.meta.strats</literal></ulink> package for all available strategies. </para> @@ -1379,7 +1379,7 @@ In a non-primary key join, at least one key. Once again, OpenJPA supports this join type with the same syntax as a primary key join. There is one restriction, however: each non-primary key column you are joining to must be controlled by a field mapping that implements the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/Joinable.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/Joinable.html"><classname> org.apache.openjpa.jdbc.meta.Joinable</classname></ulink> interface. All built in basic mappings implement this interface, including basic fields of embedded objects. OpenJPA will also respect any custom mappings that implement this @@ -1540,7 +1540,7 @@ to map entities using these strategies t <xref linkend="ref_guide_pc_oid"/> describes how to use datastore identity in JPA. OpenJPA requires a single numeric primary key column to hold datastore identity values. The -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/DataStoreIdColumn.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/DataStoreIdColumn.html"> <classname>org.apache.openjpa.persistence.jdbc.DataStoreIdColumn</classname> </ulink> annotation customizes the datastore identity column. This annotation has the following properties: @@ -1633,10 +1633,10 @@ public class LogEntry { OpenJPA supports version fields as defined by the JPA specification, but allows you to use a surrogate version column in place of a version field if you like. You map the surrogate version column with the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/VersionColumn.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/VersionColumn.html"> <classname>org.apache.openjpa.persistence.jdbc.VersionColumn</classname></ulink> annotation. You can also use the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/VersionColumns.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/VersionColumns.html"> <classname>org.apache.openjpa.persistence.jdbc.VersionColumns</classname> </ulink> annotation to declare an array of <classname>VersionColumn</classname> values. Each <classname>VersionColumn</classname> has the following properties: @@ -1774,7 +1774,7 @@ OpenJPA makes it easy to create multi-co specification includes a <classname>Column</classname> annotation, but is missing a way to declare multiple columns for a single field. OpenJPA remedies this with the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Columns.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Columns.html"> <classname>org.apache.openjpa.persistence.jdbc.Columns</classname></ulink> annotation, which contains an array of <classname>Column</classname> values. </para> @@ -1803,7 +1803,7 @@ OpenJPA rectifies this by allowing you t </emphasis> in the related type each join column links to, rather than which column. If the attribute is mapped differently in various subclass tables, OpenJPA automatically forms the proper join for the subclass record at hand. The -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/XJoinColumn.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/XJoinColumn.html"> <classname>org.apache.openjpa.persistence.jdbc.XJoinColumn</classname></ulink> annotation has all the same properties as the standard <classname>JoinColumn </classname> annotation, but adds an additional <literal> @@ -1813,7 +1813,7 @@ referencedAttributeName</literal> proper </para> <para> For compound keys, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/XJoinColumns.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/XJoinColumns.html"> <classname>org.apache.openjpa.persistence.jdbc.XJoinColumns</classname></ulink> annotation. The value of this annotation is an array of individual <classname> XJoinColumn</classname>s. @@ -1833,7 +1833,7 @@ a null embedded object and one with defa </para> <para> OpenJPA overcomes these shortcomings with the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/EmbeddedMapping.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/EmbeddedMapping.html"> <classname>org.apache.openjpa.persistence.jdbc.EmbeddedMapping</classname> </ulink> annotation. This annotation has the following properties: </para> @@ -1885,7 +1885,7 @@ allows you to override multiple mapped s </para> <para> Each -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/MappingOverride.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/MappingOverride.html"> <classname>org.apache.openjpa.persistence.jdbc.MappingOverride</classname> </ulink> annotation has the following properties: </para> @@ -2004,7 +2004,7 @@ We explore the annotations below. </indexterm> <para> The -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ContainerTable.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ContainerTable.html"> <classname>org.apache.openjpa.persistence.jdbc.ContainerTable</classname> </ulink> annotation describes a database table that holds collection (or map) elements. This annotation has the following properties: @@ -2075,11 +2075,11 @@ of the next sections. Element join columns are equivalent to standard JPA join columns, except that they represent a join to a collection or map element entity rather than a direct relation. You represent an element join column with OpenJPA's -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ElementJoinColumn.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ElementJoinColumn.html"> <classname>org.apache.openjpa.persistence.jdbc.ElementJoinColumn</classname> </ulink> annotation. To declare a compound join, enclose an array of <classname> ElementJoinColumn</classname>s in the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ElementJoinColumns.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ElementJoinColumns.html"> <classname>org.apache.openjpa.persistence.jdbc.ElementJoinColumns</classname> </ulink> annotation. </para> @@ -2112,13 +2112,13 @@ Relational databases do not guarantee th order. If you want to make sure that your collection elements are loaded in the same order they were in when last stored, you must declare an order column. An order column can be declared using OpenJPA's -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/OrderColumn"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/OrderColumn"> <classname>org.apache.openjpa.persistence.jdbc.OrderColumn</classname></ulink> annotation or the JPA 2.0 <classname>javax.persistence.OrderColumn</classname> annotation or <literal>order-column</literal> orm element as defined in <xref linkend="jpa_overview_meta_xml"/>. OpenJPA's -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/OrderColumn"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/OrderColumn"> <classname>org.apache.openjpa.persistence.jdbc.OrderColumn</classname></ulink> annotation has the following properties: </para> @@ -2274,11 +2274,11 @@ also use this annotation to represent a join columns described in <xref linkend="ref_guide_mapping_jpa_coll_joincols"/> serve for collection elements. OpenJPA's - <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/KeyColumn.html"> + <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/KeyColumn.html"> <classname>org.apache.openjpa.persistence.jdbc.KeyColumn</classname> </ulink> annotation represents a map key. To map custom multi-column keys, use the - <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/KeyColumns.html"> + <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/KeyColumns.html"> <classname>org.apache.openjpa.persistence.jdbc.KeyColumns</classname> </ulink> annotation, whose value is an array of <classname>KeyColumn</classname>s. </para> @@ -2302,10 +2302,10 @@ also use this annotation to represent a Key join columns are equivalent to standard JPA join columns, except that they represent a join to a map key entity rather than a direct relation. You represent a key join column with OpenJPA's - <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/KeyJoinColumn.html"> + <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/KeyJoinColumn.html"> <classname>org.apache.openjpa.persistence.jdbc.KeyJoinColumn</classname></ulink> annotation. To declare a compound join, enclose an array of <classname>KeyJoinColumn</classname>s in the - <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/KeyJoinColumns.html"> + <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/KeyJoinColumns.html"> <classname>org.apache.openjpa.persistence.jdbc.KeyJoinColumns</classname> </ulink> annotation. </para> @@ -2328,7 +2328,7 @@ also use this annotation to represent a </indexterm> <para> The - <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/KeyEmbeddedMapping.html"> + <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/KeyEmbeddedMapping.html"> <classname>org.apache.openjpa.persistence.jdbc.KeyEmbeddedMapping</classname> </ulink> annotation allows you to map your map field's embedded key type to your container table. This annotation has exactly @@ -2420,13 +2420,13 @@ presented in the following sections. </primary> </indexterm> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Index.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Index.html"> <classname>org.apache.openjpa.persistence.jdbc.Index</classname></ulink> annotation represents an index on the columns of a field. It is also used within the <link linkend="ref_guide_mapping_jpa_coll_table"><classname>ContainerTable </classname></link> annotation to index join columns. To index the columns of a collection element, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ElementIndex.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ElementIndex.html"> <classname> org.apache.openjpa.persistence.jdbc.ElementIndex</classname></ulink> annotation. These annotations have the following properties: </para> @@ -2470,14 +2470,14 @@ to false. </primary> </indexterm> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ForeignKey.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ForeignKey.html"> <classname>org.apache.openjpa.persistence.jdbc.ForeignKey</classname></ulink> annotation represents a foreign key on the columns of a field. It is also used within the <link linkend="ref_guide_mapping_jpa_coll_table"><classname> ContainerTable</classname></link> annotation to set a database foreign key on join columns. To set a constraint to the columns of a collection element, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ElementForeignKey.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ElementForeignKey.html"> <classname> org.apache.openjpa.persistence.jdbc.ElementForeignKey</classname> </ulink> annotation. These annotations have the following properties: </para> @@ -2517,7 +2517,7 @@ does not manifest as a database foreign <listitem> <para> <literal>ForeignKeyAction deleteAction</literal>: Value from the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ForeignKeyAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ForeignKeyAction.html"> <classname>org.apache.openjpa.persistence.jdbc.ForeignKeyAction</classname> </ulink> enum identifying the desired delete action. Defaults to <literal> RESTRICT</literal>. @@ -2526,7 +2526,7 @@ RESTRICT</literal>. <listitem> <para> <literal>ForeignKeyAction updateAction</literal>: Value from the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ForeignKeyAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ForeignKeyAction.html"> <classname>org.apache.openjpa.persistence.jdbc.ForeignKeyAction</classname> </ulink> enum identifying the desired update action. Defaults to <literal> RESTRICT</literal>. @@ -2561,7 +2561,7 @@ to discover existing foreign keys (see </primary> </indexterm> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Unique.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Unique.html"> <classname>org.apache.openjpa.persistence.jdbc.Unique</classname></ulink> annotation represents a unique constraint on the columns of a field. It is more convenient than using the <literal>uniqueConstraints</literal> property of @@ -2986,7 +2986,7 @@ restrictions. </para> <para> To persist a stream, apply the -<ulink url="../javadoc/org/apache/openjpa/persistence/Persistent.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Persistent.html"> <classname>org.apache.openjpa.persistence.Persistent</classname></ulink> annotation to either <classname>java.io.InputStream</classname> or <classname>java.io.Reader</classname> field. @@ -3119,10 +3119,10 @@ OpenJPA recognizes the following class e This extension specifies how to eagerly fetch subclass state. It overrides the global <link linkend="openjpa.jdbc.SubclassFetchMode"><literal> openjpa.jdbc.SubclassFetchMode</literal></link> property. Set the OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/SubclassFetchMode.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/SubclassFetchMode.html"> <classname>org.apache.openjpa.persistence.jdbc.SubclassFetchMode</classname> </ulink> annotation to a value from the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/FetchMode.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/FetchMode.html"> <classname>org.apache.openjpa.persistence.jdbc.FetchMode</classname> </ulink> enum: <literal>JOIN</literal>, <literal>PARALLEL</literal>, or <literal>NONE</literal>. See <xref linkend="ref_guide_perfpack_eager"/> @@ -3148,7 +3148,7 @@ openjpa.jdbc.SubclassFetchMode</literal> </seealso> </indexterm> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Strategy.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Strategy.html"> <classname>org.apache.openjpa.persistence.jdbc.Strategy</classname></ulink> class annotation allows you to specify a custom mapping strategy for your class. See <xref linkend="ref_guide_mapping_custom"/> for information on custom @@ -3175,7 +3175,7 @@ mappings. </indexterm> <para> The -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/DiscriminatorStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/DiscriminatorStrategy.html"> <classname>org.apache.openjpa.persistence.jdbc.DiscriminatorStrategy</classname> </ulink> class annotation allows you to specify a custom discriminator strategy. See <xref linkend="ref_guide_mapping_custom"/> for information on custom @@ -3202,7 +3202,7 @@ mappings. </indexterm> <para> The -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/VersionStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/VersionStrategy.html"> <classname>org.apache.openjpa.persistence.jdbc.VersionStrategy</classname> </ulink> class annotation allows you to specify a custom version strategy. See <xref linkend="ref_guide_mapping_custom"/> for information on custom @@ -3239,10 +3239,10 @@ OpenJPA recognizes the following field e This extension specifies how to eagerly fetch related objects. It overrides the global <link linkend="openjpa.jdbc.EagerFetchMode"><literal> openjpa.jdbc.EagerFetchMode</literal></link> property. Set the OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/EagerFetchMode.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/EagerFetchMode.html"> <classname>org.apache.openjpa.persistence.jdbc.EagerFetchMode</classname> </ulink> annotation to a value from the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/FetchMode.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/FetchMode.html"> <classname>org.apache.openjpa.persistence.jdbc.FetchMode</classname> </ulink> enum: <literal>JOIN</literal>, <literal>PARALLEL</literal>, or <literal>NONE</literal>. See <xref linkend="ref_guide_perfpack_eager"/> @@ -3285,14 +3285,14 @@ OpenJPA defines the following extensions <itemizedlist> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Nonpolymorphic.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Nonpolymorphic.html"> <classname>org.apache.openjpa.persistence.jdbc.Nonpolymorphic</classname> </ulink> </para> </listitem> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ElementNonpolymorphic.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ElementNonpolymorphic.html"> <classname>org.apache.openjpa.persistence.jdbc.ElementNonpolymorphic</classname> </ulink> </para> @@ -3300,7 +3300,7 @@ OpenJPA defines the following extensions </itemizedlist> <para> The value of these extensions is a constant from the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/NonpolymorphicType.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/NonpolymorphicType.html"> <classname>org.apache.openjpa.persistence.jdbc.NonpolymorphicType</classname> </ulink> enumeration. The default value, <literal>EXACT</literal>, indicates that the relation will always be of the exact declared type. A value of @@ -3353,13 +3353,13 @@ array or collection element relations, r <itemizedlist> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ClassCriteria.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ClassCriteria.html"> <classname>org.apache.openjpa.persistence.jdbc.ClassCriteria</classname></ulink> </para> </listitem> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/ElementClassCriteria.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/ElementClassCriteria.html"> <classname>org.apache.openjpa.persistence.jdbc.ElementClassCriteria</classname> </ulink> </para> @@ -3386,7 +3386,7 @@ array or collection element relations, r </indexterm> <para> OpenJPA's -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Strategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Strategy.html"> <classname>org.apache.openjpa.persistence.jdbc.Strategy</classname></ulink> extension allows you to specify a custom mapping strategy or value handler for a field. See @@ -3428,14 +3428,14 @@ strategies. </title> <para> To create a custom class mapping, write an implementation of the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/ClassStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/ClassStrategy.html"> <classname>org.apache.openjpa.jdbc.meta.ClassStrategy</classname></ulink> interface. You will probably want to extend one of the existing abstract or concrete strategies in the <literal>org.apache.openjpa.jdbc.meta.strats </literal> package. </para> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Strategy.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Strategy.html"> <classname>org.apache.openjpa.persistence.jdbc.Strategy</classname></ulink> annotation allows you to declare a custom class mapping strategy in JPA mapping metadata. Set the value of the annotation to the full class name of your custom @@ -3449,10 +3449,10 @@ OpenJPA's plugin syntax, detailed in <xr </title> <para> To define a custom discriminator or version strategy, implement the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/DiscriminatorStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/DiscriminatorStrategy.html"> <classname>org.apache.openjpa.jdbc.meta.DiscriminatorStrategy</classname> </ulink> or -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/VersionStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/VersionStrategy.html"> <classname>org.apache.openjpa.jdbc.meta.VersionStrategy</classname></ulink> interface, respectively. You might extend one of the existing abstract or concrete strategies in the <literal>org.apache.openjpa.jdbc.meta.strats @@ -3460,10 +3460,10 @@ concrete strategies in the <literal>org. </para> <para> OpenJPA includes the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/DiscriminatorStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/DiscriminatorStrategy.html"> <classname>org.apache.openjpa.persistence.jdbc.DiscriminatorStrategy</classname> </ulink> and -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/VersionStrategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/VersionStrategy.html"> <classname>org.apache.openjpa.persistence.jdbc.VersionStrategy</classname> </ulink> class annotations for declaring a custom discriminator or version strategy in JPA mapping metadata. Set the string value of these annotations to @@ -3513,7 +3513,7 @@ sections examine each. Value handlers make it trivial to map any type that you can break down into one or more simple values. All value handlers implement the <classname> org.apache.openjpa.jdbc.meta.ValueHandler</classname> interface; see its -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/ValueHandler.html"> Javadoc +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/ValueHandler.html"> Javadoc </ulink> for details. Also, examine the built-in handlers in the <filename> src/openjpa/jdbc/meta/strats</filename> directory of your OpenJPA source distribution. Use these functional implementations as examples when you @@ -3537,7 +3537,7 @@ create your own value handlers. </indexterm> <para> OpenJPA interacts with persistent fields through the -<ulink url="../javadoc/org/apache/openjpa/jdbc/meta/FieldStrategy"><classname> +<ulink url="../../apidocs/org/apache/openjpa/jdbc/meta/FieldStrategy"><classname> org.apache.openjpa.jdbc.meta.FieldStrategy</classname></ulink> interface. You can implement this interface yourself to create a custom field strategy, or extend one of the existing abstract or concrete strategies in the <literal> @@ -3576,7 +3576,7 @@ defaults in detail. Your other option is to explicitly install a custom value handler or strategy on a particular field. To do so, specify the full name of your implementation class in the proper mapping metadata extension. OpenJPA includes the -<ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Strategy.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/jdbc/Strategy.html"> <classname>org.apache.openjpa.persistence.jdbc.Strategy</classname></ulink> annotation. You can configure the named strategy or handler's bean properties in these extensions using OpenJPA's plugin format (see @@ -3610,7 +3610,7 @@ openjpa.OrphanedKeyAction</literal></lin action to take when OpenJPA encounters an orphaned key. You can set this plugin string (see <xref linkend="ref_guide_conf_plugins"/>) to a custom implementation of the -<ulink url="../javadoc/org/apache/openjpa/event/OrphanedKeyAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/OrphanedKeyAction.html"> <classname> org.apache.openjpa.event.OrphanedKeyAction</classname></ulink> interface, or use one of the built-in options: </para> @@ -3619,7 +3619,7 @@ interface, or use one of the built-in op <para> <literal>log</literal>: This is the default setting. This option logs a message for each orphaned key. It is an alias for the -<ulink url="../javadoc/org/apache/openjpa/event/LogOrphanedKeyAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/LogOrphanedKeyAction.html"> <classname>org.apache.openjpa.event.LogOrphanedKeyAction</classname></ulink> class, which has the following additional properties: </para> @@ -3643,7 +3643,7 @@ openjpa.Runtime</literal>. <literal>exception</literal>: Throw an <classname> EntityNotFoundException</classname> when OpenJPA discovers an orphaned key. This is an alias for the -<ulink url="../javadoc/org/apache/openjpa/event/ExceptionOrphanedKeyAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/ExceptionOrphanedKeyAction.html"> <classname>org.apache.openjpa.event.ExceptionOrphanedKeyAction</classname> </ulink> class. </para> @@ -3651,7 +3651,7 @@ orphaned key. This is an alias for the <listitem> <para> <literal>none</literal>: Ignore orphaned keys. This is an alias for the -<ulink url="../javadoc/org/apache/openjpa/event/NoneOrphanedKeyAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/NoneOrphanedKeyAction.html"> <classname>org.apache.openjpa.event.NoneOrphanedKeyAction</classname></ulink> class. </para> Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_meta.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_meta.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_meta.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_meta.xml Thu Jun 28 09:32:10 2018 @@ -45,7 +45,7 @@ The <link linkend="openjpa.MetaDataFacto </literal></link> configuration property controls metadata loading and storing. This property takes a plugin string (see <xref linkend="ref_guide_conf_plugins"/>) describing a concrete -<ulink url="../javadoc/org/apache/openjpa/meta/MetaDataFactory.html"> +<ulink url="../../apidocs/org/apache/openjpa/meta/MetaDataFactory.html"> <classname>org.apache.openjpa.meta.MetaDataFactory</classname></ulink> implementation. A metadata factory can load mapping information as well as persistence metadata, or it can leave mapping information to a separate @@ -57,7 +57,7 @@ following built-in metadata factories: <listitem> <para> <literal>jpa</literal>: Standard JPA metadata. This is an alias for the -<ulink url="../javadoc/org/apache/openjpa/persistence/PersistenceMetaDataFactory.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/PersistenceMetaDataFactory.html"> <classname> org.apache.openjpa.persistence.PersistenceMetaDataFactory</classname></ulink>. </para> @@ -220,7 +220,7 @@ JPA defines <literal>Basic</literal>, <l </literal>, <literal>ManyToOne</literal>, and <literal>OneToOne</literal> persistence strategies for direct field values. OpenJPA supports all of these standard strategies, but adds one of its own: <literal>Persistent</literal>. -The <ulink url="../javadoc/org/apache/openjpa/persistence/Persistent.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/Persistent.html"> <classname>org.apache.openjpa.persistence.Persistent</classname></ulink> metadata annotation can represent any direct field value, including custom types. It has the following properties: @@ -286,7 +286,7 @@ JPA standardizes support for collections OneToMany</literal> and <literal>ManyToMany</literal> persistence strategies. OpenJPA supports these strategies, and may be extended for other strategies as well. For extended strategies, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/PersistentCollection.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/PersistentCollection.html"> <classname>org.apache.openjpa.persistence.PersistentCollection</classname></ulink> metadata annotation to represents any persistent collection field. It has the following properties: @@ -342,7 +342,7 @@ ManyToMany</classname></link>. Defaults <para> JPA has limited support for maps. If you extend JPA's standard map support to encompass new mappings, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/PersistentMap.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/PersistentMap.html"> <classname>org.apache.openjpa.persistence.PersistentMap</classname></ulink> metadata annotation to represent your custom persistent map fields. It has the following properties: @@ -448,9 +448,9 @@ OpenJPA recognizes the following class e </seealso> </indexterm> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/FetchGroups.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/FetchGroups.html"> <classname>org.apache.openjpa.persistence.FetchGroups</classname></ulink> and -<ulink url="../javadoc/org/apache/openjpa/persistence/FetchGroup.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/FetchGroup.html"> <classname>org.apache.openjpa.persistence.FetchGroup</classname></ulink> annotations allow you to define fetch groups in your JPA entities. <xref linkend="ref_guide_fetch"/> discusses OpenJPA's support for fetch @@ -482,7 +482,7 @@ extensions allow individual classes to o </para> <para> OpenJPA defines the -<ulink url="../javadoc/org/apache/openjpa/persistence/DataCache.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/DataCache.html"> <classname>org.apache.openjpa.persistence.DataCache</classname></ulink> annotation for caching information. This annotation has the following properties: @@ -536,7 +536,7 @@ modifications. </para> <para> OpenJPA defines the -<ulink url="../javadoc/org/apache/openjpa/persistence/DetachedState.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/DetachedState.html"> <classname>org.apache.openjpa.persistence.DetachedState</classname></ulink> annotation for controlling detached state. When used to annotate a class, <classname>DetachedState</classname> recognizes the following properties: @@ -611,21 +611,21 @@ JPA entities: <itemizedlist> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/Dependent.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Dependent.html"> <classname> org.apache.openjpa.persistence.Dependent</classname></ulink>: Marks a direct relation as dependent. </para> </listitem> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/ElementDependent.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/ElementDependent.html"> <classname> org.apache.openjpa.persistence.ElementDependent</classname></ulink> : Marks the entity elements of a collection, array, or map field as dependent. </para> </listitem> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/KeyDependent.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/KeyDependent.html"> <classname> org.apache.openjpa.persistence.KeyDependent</classname></ulink>: Marks the key entities in a map field as dependent. </para> @@ -656,7 +656,7 @@ Marks the key entities in a map field as </secondary> </indexterm> <para> -The <ulink url="../javadoc/org/apache/openjpa/persistence/LoadFetchGroup.html"> +The <ulink url="../../apidocs/org/apache/openjpa/persistence/LoadFetchGroup.html"> <classname>org.apache.openjpa.persistence.LoadFetchGroup</classname></ulink> annotation specifies a field's load fetch group. <xref linkend="ref_guide_fetch"/> discusses OpenJPA's support for fetch groups @@ -684,7 +684,7 @@ annotation in particular. </indexterm> <para> This boolean extension, denoted by the OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/LRS.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/persistence/LRS.html"><classname> org.apache.openjpa.persistence.LRS</classname></ulink> annotation, indicates that a field should use OpenJPA's special large result set collection or map proxies. A complete description of large result set proxies is available @@ -712,7 +712,7 @@ in <xref linkend="ref_guide_pc_scos_prox <para> This extension names the inverse field in a logical bidirectional relation. To create a logical bidirectional relation in OpenJPA, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/InverseLogical.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/InverseLogical.html"> <classname>org.apache.openjpa.persistence.InverseLogical</classname></ulink> annotation. We discuss logical bidirectional relations and this extension in detail in <xref linkend="ref_guide_inverses"/>. @@ -750,10 +750,10 @@ existing persistent objects; new object </para> <para> To mark a field read-only in JPA metadata, set the -<ulink url="../javadoc/org/apache/openjpa/persistence/ReadOnly.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/ReadOnly.html"> <classname>org.apache.openjpa.persistence.ReadOnly</classname></ulink> annotation to an -<ulink url="../javadoc/org/apache/openjpa/persistence/UpdateAction.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/UpdateAction.html"> <classname>org.apache.openjpa.persistence.UpdateAction</classname></ulink> enum value. The <classname>UpdateAction</classname> enum includes: </para> @@ -851,19 +851,19 @@ array, and map elements, and map keys, r <itemizedlist> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/Type.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Type.html"><classname> org.apache.openjpa.persistence.Type</classname></ulink> </para> </listitem> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/ElementType.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/ElementType.html"> <classname>org.apache.openjpa.persistence.ElementType</classname></ulink> </para> </listitem> <listitem> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/KeyType.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/persistence/KeyType.html"><classname> org.apache.openjpa.persistence.KeyType</classname></ulink> </para> </listitem> @@ -889,7 +889,7 @@ org.apache.openjpa.persistence.KeyType</ </indexterm> <para> The OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/Externalizer.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Externalizer.html"> <classname>org.apache.openjpa.persistence.Externalizer</classname></ulink> annotation names a method to transform a field value into a value of another type. See <xref linkend="ref_guide_pc_extern"/> for details. @@ -915,7 +915,7 @@ another type. See <xref linkend="ref_gui </indexterm> <para> The OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/Factory.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Factory.html"><classname> org.apache.openjpa.persistence.Factory</classname></ulink> annotation names a method to re-create a field value from its externalized form. See <xref linkend="ref_guide_pc_extern"/> for details. @@ -941,7 +941,7 @@ names a method to re-create a field valu </indexterm> <para> The OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/ExternalValues.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/ExternalValues.html"> <classname>org.apache.openjpa.persistence.ExternalValues</classname></ulink> annotation declares values for transformation of simple fields to different constant values in the datastore. See Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_optimization.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_optimization.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_optimization.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_optimization.xml Thu Jun 28 09:32:10 2018 @@ -159,7 +159,7 @@ features in a transaction that will dele number of objects you can set <literal>LargeTransaction</literal> to true and perform periodic flushes during your transaction to reduce its memory requirements. See the Javadoc: -<ulink url="../javadoc/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> OpenJPAEntityManager.setTrackChangesByType</ulink>. Note that transactions in large mode have to more aggressively flush items from the data cache. <para> @@ -168,7 +168,7 @@ accessed by other transactions, for exam month, you can turn off population of the data cache so that the transaction doesn't fill the entire data cache with objects that won't be accessed again. Again, see the Javadoc: -<ulink url="../javadoc/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> OpenJPAEntityManager.setPopulateDataCache</ulink> </para> </entry> Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_pc.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_pc.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_pc.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_pc.xml Thu Jun 28 09:32:10 2018 @@ -629,7 +629,7 @@ persistent objects for you through a sur <para> You can control how your JPA datastore identity value is generated through OpenJPA's -<ulink url="../javadoc/org/apache/openjpa/persistence/DataStoreId.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/DataStoreId.html"> <classname>org.apache.openjpa.persistence.DataStoreId</classname></ulink> class annotation. This annotation has <literal>strategy</literal> and <literal> generator</literal> properties that mirror the same-named properties on the @@ -659,7 +659,7 @@ public class LineItem { </example> <para> Internally, OpenJPA uses the public -<ulink url="../javadoc/org/apache/openjpa/util/Id.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/util/Id.html"><classname> org.apache.openjpa.util.Id</classname></ulink> class for datastore identity objects. When writing OpenJPA plugins, you can manipulate datastore identity objects by casting them to this class. You can also create your own <classname> @@ -882,7 +882,7 @@ class code, you can set the <literal>@Id </para> <para> The application identity tool can be invoked via its Java class, -<ulink url="../javadoc/org/apache/openjpa/enhance/ApplicationIdTool"> +<ulink url="../../apidocs/org/apache/openjpa/enhance/ApplicationIdTool"> <classname>org.apache.openjpa.enhance.ApplicationIdTool</classname></ulink>. </para> <note> @@ -1056,7 +1056,7 @@ relations that also share datastore stor </para> <para> OpenJPA also allows you to define purely logical bidirectional relations. The -<ulink url="../javadoc/org/apache/openjpa/persistence/InverseLogical.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/InverseLogical.html"> <classname>org.apache.openjpa.persistence.InverseLogical</classname></ulink> annotation names a logical inverse in JPA metadata. </para> @@ -1388,7 +1388,7 @@ collection and map methods, and to updat </para> <para> In order to use large result set proxies in JPA, add the -<ulink url="../javadoc/org/apache/openjpa/persistence/LRS.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/persistence/LRS.html"><classname> org.apache.openjpa.persistence.LRS</classname></ulink> annotation to the persistent field. </para> @@ -1463,7 +1463,7 @@ public class Company { </indexterm> <para> OpenJPA manages proxies through the -<ulink url="../javadoc/org/apache/openjpa/util/ProxyManager.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/util/ProxyManager.html"><classname> org.apache.openjpa.util.ProxyManager</classname></ulink> interface. OpenJPA includes a default proxy manager, the <classname> org.apache.openjpa.util.ProxyManagerImpl</classname> (with a plugin alias name @@ -1494,7 +1494,7 @@ improve performance of some applications operations on collections without requiring them to be loaded. Delayed proxies are loaded when an operation is performed that requires loading, such as iteration, size, serialization, and indexOf. They can also be loaded by casting the -proxy to a <ulink url="../javadoc/org/apache/openjpa/util/DelayedProxy.html"><classname> +proxy to a <ulink url="../../apidocs/org/apache/openjpa/util/DelayedProxy.html"><classname> org.apache.openjpa.util.DelayedProxy</classname></ulink> and invoking the <methodname>load</methodname> method. If a broker factory is available after detaching the owning entity, a collection may be available for delayed loading after the persistence context has been @@ -1539,7 +1539,7 @@ each of B's setters with the value from If you have custom classes that must be proxied and do not meet these requirements, OpenJPA allows you to define your own proxy classes and your own proxy manager. See the <literal>openjpa.util</literal> package -<ulink url="../javadoc/">Javadoc</ulink> for details on the interfaces involved, +<ulink url="../../apidocs/">Javadoc</ulink> for details on the interfaces involved, and the utility classes OpenJPA provides to assist you. </para> <para> @@ -1651,14 +1651,14 @@ JPA cannot have externalizers. </note> <para> The OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/Externalizer.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Externalizer.html"> <classname>org.apache.openjpa.persistence.Externalizer</classname></ulink> annotation sets the name of a method that will be invoked to convert the field into its external form for database storage. You can specify either the name of a non-static method, which will be invoked on the field value, or a static method, which will be invoked with the field value as a parameter. Each method can also take an optional -<ulink url="../javadoc/org/apache/openjpa/kernel/StoreContext.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/kernel/StoreContext.html"><classname> StoreContext</classname></ulink> parameter for access to a persistence context. The return value of the method is the field's external form. By default, OpenJPA assumes that all named methods belong to the field value's class (or its @@ -1743,13 +1743,13 @@ public static String AnyClass.toString(C </table> <para> The OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/Factory.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Factory.html"><classname> org.apache.openjpa.persistence.Factory</classname></ulink> annotation contains the name of a method that will be invoked to instantiate the field from the external form stored in the database. Specify a static method name. The method will be invoked with the externalized value and must return an instance of the field type. The method can also take an optional -<ulink url="../javadoc/org/apache/openjpa/kernel/StoreContext.html"><classname> +<ulink url="../../apidocs/org/apache/openjpa/kernel/StoreContext.html"><classname> StoreContext</classname></ulink> parameter for access to a persistence context. If a factory is not specified, OpenJPA will use the constructor of the field type that takes a single argument of the external type, or will throw an @@ -1851,7 +1851,7 @@ If your custom field type is mutable and date class, OpenJPA will not be able to detect changes to the field. You must mark the field dirty manually, or create a custom field proxy. See -<ulink url="../javadoc/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> <methodname>OpenJPAEntityManager.dirty</methodname></ulink> for how to mark a field dirty manually in JPA. See <xref linkend="ref_guide_pc_scos_proxy"/> for a discussion of proxies. @@ -1983,7 +1983,7 @@ primitive wrappers, and Strings), to oth </para> <para> Use the OpenJPA -<ulink url="../javadoc/org/apache/openjpa/persistence/ExternalValues.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/ExternalValues.html"> <classname>org.apache.openjpa.persistence.ExternalValues</classname></ulink> annotation to define external value translations. The values are defined in a format similar to that of <link linkend="ref_guide_conf_plugins"> @@ -1995,7 +1995,7 @@ true=T,false=F</literal>. </para> <para> If the type of the datastore value is different from the field's type, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/Type.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/Type.html"> <classname>org.apache.openjpa.persistence.Type</classname></ulink> annotation to define the datastore type. </para> @@ -2057,11 +2057,11 @@ active fetch groups when loading objects </para> <para> You create fetch groups with the -<ulink url="../javadoc/org/apache/openjpa/persistence/FetchGroup.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/FetchGroup.html"> <classname>org.apache.openjpa.persistence.FetchGroup</classname></ulink> annotation. If your class only has one custom fetch group, you can place this annotation directly on the class declaration. Otherwise, use the -<ulink url="../javadoc/org/apache/openjpa/persistence/FetchGroups.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/FetchGroups.html"> <classname>org.apache.openjpa.persistence.FetchGroups</classname></ulink> annotation to declare an array of individual <classname>FetchGroup</classname> values. The <classname>FetchGroup</classname> annotation has the following @@ -2100,7 +2100,7 @@ include in this group. </itemizedlist> <para> As you might expect, listing a -<ulink url="../javadoc/org/apache/openjpa/persistence/FetchAttribute.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/FetchAttribute.html"> <classname>org.apache.openjpa.persistence.FetchAttribute</classname></ulink> within a <classname>FetchGroup</classname> includes the corresponding persistent field or property in the fetch group. Each <classname>FetchAttribute</classname> @@ -2166,7 +2166,7 @@ accessed. </para> <para> Use OpenJPA's -<ulink url="../javadoc/org/apache/openjpa/persistence/LoadFetchGroup.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/LoadFetchGroup.html"> <classname>org.apache.openjpa.persistence.LoadFetchGroup</classname></ulink> annotation to specify the load fetch group of any persistent field. The value of the annotation is the name of a declared fetch group whose members should be @@ -2244,7 +2244,7 @@ the fetch depth to something less than t OpenJPA's <classname>OpenJPAEntityManager</classname> and <classname> OpenJPAQuery</classname> extensions to the standard <classname>EntityManager </classname> and <classname>Query</classname> interfaces provide access to a -<ulink url="../javadoc/org/apache/openjpa/persistence/FetchPlan.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/FetchPlan.html"> <classname>org.apache.openjpa.persistence.FetchPlan</classname></ulink> object. The <classname>FetchPlan</classname> maintains the set of active fetch groups and the maximum fetch depth. It begins with the groups and depth defined in the Modified: openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_remote.xml URL: http://svn.apache.org/viewvc/openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_remote.xml?rev=1834586&r1=1834585&r2=1834586&view=diff ============================================================================== --- openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_remote.xml (original) +++ openjpa/branches/2.4.x/openjpa-project/src/doc/manual/ref_guide_remote.xml Thu Jun 28 09:32:10 2018 @@ -108,7 +108,7 @@ the following javax.persistence.EntityMa public void detach(Object) </programlisting> <para> -<ulink url="../javadoc/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> <classname>OpenJPAEntityManager</classname></ulink>, however, provides additional detach methods. </para> @@ -400,7 +400,7 @@ all <literal>Large Result Sets</literal> <para> You can also alter the set of fields that will be included in the detached graph at runtime. -<ulink url="../javadoc/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> +<ulink url="../../apidocs/org/apache/openjpa/persistence/OpenJPAEntityManager.html"> <classname>OpenJPAEntityManager</classname></ulink>s expose the following APIs for controlling detached state: </para> @@ -521,7 +521,7 @@ To enable remote events, you must config <para> When a <literal>RemoteCommitProvider</literal> is properly configured, you can register -<ulink url="../javadoc/org/apache/openjpa/event/RemoteCommitListener.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/RemoteCommitListener.html"> <classname>RemoteCommitListener</classname></ulink>s that will be alerted with a list of modified object ids whenever a transaction on a remote machine successfully commits. @@ -784,10 +784,10 @@ provider, we modify the previous example <para> You can develop additional mechanisms for remote event notification be by creating an implementation of the -<ulink url="../javadoc/org/apache/openjpa/event/RemoteCommitProvider.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/RemoteCommitProvider.html"> <classname> RemoteCommitProvider</classname></ulink> interface, possibly by extending the -<ulink url="../javadoc/org/apache/openjpa/event/AbstractRemoteCommitProvider.html"> +<ulink url="../../apidocs/org/apache/openjpa/event/AbstractRemoteCommitProvider.html"> <classname>AbstractRemoteCommitProvider</classname></ulink> abstract class.. </para> </section>
