Author: mmcallis
Date: 2008-02-06 02:04:41 -0500 (Wed, 06 Feb 2008)
New Revision: 9796
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
Log:
rephrasing 3.6. Disabling Dynamic Proxy Un-wrapping
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-02-06
06:11:36 UTC (rev 9795)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-06
07:04:41 UTC (rev 9796)
@@ -250,7 +250,7 @@
</para>
</sect1>
<sect1>
- <title>Setting up proxy settings</title>
+ <title>Configuring proxy settings</title>
<para>There are a couple of scenarios where you will need your proxy to be
correctly defined at the JVM
level so that you can access documents from Internet. It could be to get the
thirdparty libraries if you
decided to build JBoss Portal from the sources, to access RSS feeds or weather
information in the samples
@@ -261,19 +261,20 @@
is enough.</para>
</sect1>
<sect1>
- <title>Disabling dynamic proxy unwrapping</title>
- <para>JBoss Portal use the JBoss Microkernel for the service
infrastructure. The JBoss Microkernel provides
- injection of services into other services, also known as wiring. Unfortunately
it is only possible to inject
- dynamic proxies that talks to the MBeanServer due to the fact the Microkernel is
JMX based. The overhead
- at runtime is minimal since the Microkernel implementation is highly optimized,
however when it is used
- with Java 5 a noticeable bottleneck appears due to the fact that the
implementation
- of the JMX API classes <emphasis>javax.management.*</emphasis>
provided by the Java Platform performs synchronization. This does
- not happen under JDK 1.4 since those classes are implemented by JBoss
MX.</para>
- <para>JBoss Portal services use a special kind of Model MBean called
JBossServiceModelMBean which allows to
- unwrap the injected dynamic proxies and replace them by the real POJO services.
This allows to remove the
- bottleneck with Java 5 and provide an extra boost of performances on JDK 1.4. By
default that feature
- is enabled but it is possible to disabled it using command line
arguments.</para>
- <programlisting><![CDATA[
->run.sh -Dportal.kernel.no_proxies=false]]></programlisting>
+ <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,
also known as wiring. It is only possible to inject
+ dynamic proxies that talk to the MBeanServer, due to the Microkernel being JMX
based. The overhead
+ at runtime is minimal since the Microkernel implementation is highly optimized;
however, when it is used
+ with Java 5, a noticeable bottleneck appears due to the fact that the
implementation
+ of the JMX API classes, <emphasis>javax.management.*</emphasis>,
provided by the Java Platform, performs synchronization. This does not occur under JDK 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 real plain old java object (POJO)
services. This allows the removal of the bottleneck with Java 5, and also provides a
performance boost on JDK 1.4. By default this feature is enabled, but it is possible to
disabled is using the following command:
+ </para>
+ <para>
+<screen><![CDATA[
+./run.sh -Dportal.kernel.no_proxies=false]]>
+</screen>
+</para>
</sect1>
</chapter>
Show replies by date