Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Removed OC4J support (including documentation references)

Browse Source
This commit is contained in:
Juergen Hoeller
2013-03-19 14:53:26 +01:00
parent a03d125b4e
commit 9c52ae9558
18 changed files with 822 additions and 632 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/reference/docbook/aop.xml
View File

@@ -3589,13 +3589,6 @@ http://www.springframework.org/schema/context
<entry><para><classname>WebSphereLoadTimeWeaver</classname></para></entry>
</row>
<row>
<entry><para>Running in <link
xl:href="http://www.oracle.com/technology/products/oc4j/index.html">Oracle's
OC4J</link></para></entry>
<entry><para><classname>OC4JLoadTimeWeaver</classname></para></entry>
</row>
<row>
<entry><para>Running in <link xl:href="http://glassfish.dev.java.net/">GlassFish</link></para></entry>
<entry><para><classname>GlassFishLoadTimeWeaver</classname></para></entry>
@@ -3854,10 +3847,11 @@ TR: REVISED, PLS REVIEW. Chnaged the last one to *inside*--> is recommended
</section>
<section xml:id="aop-aj-ltw-environments-weblogic-oc4j-resin-glassfish-jboss">
<title>WebLogic, WebSphere, OC4J, Resin, GlassFish, JBoss</title>
<title>WebLogic, WebSphere, Resin, GlassFish, JBoss</title>
<para>Recent versions of BEA WebLogic (version 10 and above), IBM WebSphere Application Server (version 7 and above),
Oracle Containers for Java EE (OC4J 10.1.3.1 and above), Resin (3.1 and above) and JBoss (5.x or above)
<para>Recent versions of WebLogic Server (version 10 and above),
IBM WebSphere Application Server (version 7 and above),
Resin (3.1 and above) and JBoss (5.x or above)
provide a ClassLoader that is capable of local instrumentation.
Spring's native LTW leverages such ClassLoaders to enable AspectJ weaving.
You can enable LTW by simply activating load-time weaving

4
src/reference/docbook/orm.xml
View File

@@ -1474,14 +1474,14 @@ TR: OK AS IS. The requirement is to provide the classloader for the runtime envi
<para>Refer to <xref linkend="aop-aj-ltw-spring" /> in the AOP chapter for more insight regarding the
<interfacename>LoadTimeWeaver</interfacename> implementations and their setup, either generic or customized to
various platforms (such as Tomcat, WebLogic, OC4J, GlassFish, Resin and JBoss).</para>
various platforms (such as Tomcat, WebLogic, GlassFish, Resin and JBoss).</para>
<para>As described in the aforementioned section, you can configure a context-wide <interfacename>LoadTimeWeaver</interfacename>
using the <interfacename>@EnableLoadTimeWeaving</interfacename> annotation of <literal>context:load-time-weaver</literal> XML element.
Such a global weaver is picked up by all JPA <classname>LocalContainerEntityManagerFactoryBeans</classname>
automatically. This is the preferred way of setting up a load-time weaver, delivering autodetection of the platform
(WebLogic, OC4J, GlassFish, Tomcat, Resin, JBoss or VM agent) and automatic propagation of the weaver to all weaver-aware beans:</para>
(WebLogic, GlassFish, Tomcat, Resin, JBoss or VM agent) and automatic propagation of the weaver to all weaver-aware beans:</para>
<programlisting language="xml">&lt;context:load-time-weaver/&gt;
&lt;bean id="emf" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"&gt;

32
src/reference/docbook/transaction.xml
View File

@@ -2427,15 +2427,14 @@ txManager.commit(status);</programlisting>
<para>Spring's <classname>JtaTransactionManager</classname> is the
standard choice to run on Java EE application servers, and is known to
work on all common servers. Advanced functionality such as transaction
suspension works on many servers as well -- including GlassFish, JBoss,
Geronimo, and Oracle OC4J -- without any special configuration required.
suspension works on many servers as well -- including GlassFish, JBoss
and Geronimo -- without any special configuration required.
However, for fully supported transaction suspension and further advanced
integration, Spring ships special adapters for IBM WebSphere, BEA WebLogic
Server, and Oracle OC4J. These adapters are discussed in the following
sections.</para>
integration, Spring ships special adapters for WebLogic Server and
WebSphere. These adapters are discussed in the following sections.</para>
<para><emphasis>For standard scenarios, including WebLogic Server,
WebSphere and OC4J, consider using the convenient
<para><emphasis>For standard scenarios, including WebLogic Server and
WebSphere, consider using the convenient
<literal>&lt;tx:jta-transaction-manager/&gt;</literal> configuration
element.</emphasis> When configured, this element automatically detects
the underlying server and chooses the best transaction manager available
@@ -2459,7 +2458,7 @@ txManager.commit(status);</programlisting>
</section>
<section xml:id="transaction-application-server-integration-weblogic">
<title>BEA WebLogic Server</title>
<title>Oracle WebLogic Server</title>
<para>On WebLogic Server 9.0 or above, you typically would use the
<classname>WebLogicJtaTransactionManager</classname> instead of the
@@ -2472,23 +2471,6 @@ txManager.commit(status);</programlisting>
transactions in all cases.</para>
</section>
<section xml:id="transaction-application-server-integration-oc4j">
<title>Oracle OC4J</title>
<para>Spring ships a special adapter class for OC4J 10.1.3 or later
called <classname>OC4JJtaTransactionManager</classname>. This class is
analogous to the <classname>WebLogicJtaTransactionManager</classname>
class discussed in the previous section, providing similar value-adds on
OC4J: transaction names and per-transaction isolation levels.</para>
<para>The full JTA functionality, including transaction suspension,
works fine with Spring's <classname>JtaTransactionManager</classname> on
OC4J as well. The special
<classname>OC4JJtaTransactionManager</classname> adapter simply provides
value-adds beyond standard JTA.</para>
</section>
</section>
<section xml:id="transaction-solutions-to-common-problems">
<title>Solutions to common problems</title>