[seam-commits] Seam SVN: r7691 - trunk/doc/reference/en/modules.
Author: jbalunas(a)redhat.com
Date: 2008-03-25 10:20:59 -0400 (Tue, 25 Mar 2008)
New Revision: 7691
Modified:
trunk/doc/reference/en/modules/configuration.xml
trunk/doc/reference/en/modules/persistence.xml
Log:
Reverted changes made for JPA - JBSEAM-1946.
This will be handled differently.
Modified: trunk/doc/reference/en/modules/configuration.xml
===================================================================
--- trunk/doc/reference/en/modules/configuration.xml 2008-03-25 14:18:04 UTC (rev 7690)
+++ trunk/doc/reference/en/modules/configuration.xml 2008-03-25 14:20:59 UTC (rev 7691)
@@ -427,50 +427,6 @@
</sect2>
</sect1>
-
- <sect1 id="alt-jpa-providers">
- <title>Using Alternate JPA Providers</title>
-
- <para> Seam comes packaged and configured with Hibernate as the primary JPA
provider.
- This helps with the <emphasis>Configuration by Exception</emphasis>
concept.
- If you require using a different JPA provider you must tell
<literal>seam</literal>
- about it.
- </para>
-
- <para>This can be be done in one of two ways:
- <itemizedlist>
- <listitem>
- <para>Update your application's
<literal>components.xml</literal>
- so that the generic
<literal>PersistenceProvider</literal> takes
- precedence over the hibernate version. Simply add the following
- to the file:
- <programlisting><![CDATA[<component
name="org.jboss.seam.persistence.persistenceProvider"
- class="org.jboss.seam.persistence.PersistenceProvider"
- scope="stateless">
-</component>]]></programlisting>
- </para>
- </listitem>
- <listitem>
- <para>If you want to take advantage of your JPA providers
- non-standard features you will need to write you own implementation
of
- the <literal>PersistenceProvider</literal>. Use
- <literal>HibernatePersistenceProvider</literal> as a
starting
- point (don't forget to provide it to the community :). Then you
- will need to tell <literal>seam</literal> to use it as
before.
- <programlisting><![CDATA[<component
name="org.jboss.seam.persistence.persistenceProvider"
- class="org.your.package.YourPersistenceProvider">
-</component>]]></programlisting>
-
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>All that is left is updating the
<literal>persistence.xml</literal>
- file with the correct provider class, and what ever properties it
- needs. Don't forget to package your new provider's jar files in the
- application if they are needed.
- </para>
- </sect1>
<sect1>
<title>Configuring Seam in Java EE 5</title>
Modified: trunk/doc/reference/en/modules/persistence.xml
===================================================================
--- trunk/doc/reference/en/modules/persistence.xml 2008-03-25 14:18:04 UTC (rev 7690)
+++ trunk/doc/reference/en/modules/persistence.xml 2008-03-25 14:20:59 UTC (rev 7691)
@@ -484,8 +484,7 @@
API via the <literal>getDelegate()</literal> method. Naturally,
the most interesting
vendor is Hibernate, and the most powerful delegate interface is
<literal>org.hibernate.Session</literal>. You'd be nuts to
use anything else. Trust
- me, I'm not biased at all. For configuring alternate JPA providers see
- <link linkend="alt-jpa-providers">Using Alternate JPA
Providers</link>
+ me, I'm not biased at all.
</para>
<para>