Author: mmcallis Date: 2008-06-12 22:53:31 -0400 (Thu, 12 Jun 2008) New Revision: 11016 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/supported.xml Log: trademark symbols for JDK Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-06-13 02:47:32 UTC (rev 11015) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-06-13 02:53:31 UTC (rev 11016) @@ -263,7 +263,7 @@ </sect1> <sect1> <title>Disabling Dynamic Proxy Un-wrapping</title> - <para>JBoss Portal uses the JBoss Microkernel for the service infrastructure. The JBoss Microkernel provides injection of services into other services, otherwise known as wiring. Due to the Microkernel being <trademark class="trade">JMX</trademark> based, it is only possible to inject dynamic proxies that talk to the MBeanServer. The overhead at runtime is minimal since the Microkernel implementation is highly optimized; however, when it is used with Java 5, a noticeable bottleneck occurs due to the fact that the implementation of the JMX API classes, <emphasis>javax.management.*</emphasis>, provided by the Java Platform, perform synchronization. This does not occur under JDK 1.4, since those classes are implemented by JBoss MX. + <para>JBoss Portal uses the JBoss Microkernel for the service infrastructure. The JBoss Microkernel provides injection of services into other services, otherwise known as wiring. Due to the Microkernel being <trademark class="trade">JMX</trademark> based, it is only possible to inject dynamic proxies that talk to the MBeanServer. The overhead at runtime is minimal since the Microkernel implementation is highly optimized; however, when it is used with Java 5, a noticeable bottleneck occurs due to the fact that the implementation of the JMX API classes, <emphasis>javax.management.*</emphasis>, provided by the Java Platform, perform synchronization. This does not occur under <trademark class="trade">JDK</trademark> 1.4, since those classes are implemented by JBoss MX. </para> <para> JBoss Portal services use a special kind of Model MBean called <emphasis>JBossServiceModelMBean</emphasis>, which allows the un-wrapping of injected dynamic proxies, and replaces them with Plain Old Java Object (POJO) services. This removes the bottleneck when using Java 5, and also provides a performance boost on JDK 1.4. By default this feature is enabled, but it is possible to disable. To do this on Linux operating systems, change into the <filename>$JBOSS_HOME/bin/</filename> directory and run the following command: Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/supported.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/supported.xml 2008-06-13 02:47:32 UTC (rev 11015) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/supported.xml 2008-06-13 02:53:31 UTC (rev 11016) @@ -22,7 +22,7 @@ <title>Minimum System Requirements</title> <para> <itemizedlist> - <listitem>JDK 5 (JDK 6 is not part of the test platform)</listitem> + <listitem><trademark trade="class">JDK</trademark> 5 (JDK 6 is not part of the test platform)</listitem> <listitem>512 MB RAM</listitem> <listitem>100 MB hard disk space</listitem> <listitem>400 MHz CPU</listitem>