Author: mmcallis Date: 2008-06-12 20:36:07 -0400 (Thu, 12 Jun 2008) New Revision: 11011 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/identity.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/portalapi.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml Log: removing unnecessary Java trademark symbols 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 00:24:24 UTC (rev 11010) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-06-13 00:36:07 UTC (rev 11011) @@ -257,13 +257,13 @@ decided to build JBoss Portal from the sources, to access RSS feeds or weather information in the samples portlet we provide or for your own needs.</para> <para>To configure the proxy settings, you need to know the proxy host and the port to use. Then, - add them when starting <trademark class="trade">Java</trademark>.</para> + add them when starting Java.</para> <para>Usually setting up JAVA_OPTS environment variable to <literal>-Dhttp.proxyHost=YOUR_PROXY_HOST -Dhttp.proxyPort=YOUR_PROXY_PORT</literal> is enough.</para> </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 JMX 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 <trademark class="trade">Java</trademark> 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 JMX 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> <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/identity.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/identity.xml 2008-06-13 00:24:24 UTC (rev 11010) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/identity.xml 2008-06-13 00:36:07 UTC (rev 11011) @@ -386,7 +386,7 @@ <sect1> <title>Identity configuration</title> <para>In order to understand identity configuration you need to understand its architecture. - Different identity services like UserModule, RoleModule and etc are just plain <trademark class="trade">Java</trademark> classes that are instantiated and exposed + Different identity services like UserModule, RoleModule and etc are just plain Java classes that are instantiated and exposed by the portal. So an *example* of UserModule service could be a plain Java bean object that would be: <itemizedlist> <listitem><emphasis role="bold">Instantiated</emphasis> using reflection</listitem> @@ -566,7 +566,7 @@ </listitem> <listitem> <para> - <emphasis role="bold">class</emphasis> - <trademark class="trade">Java</trademark> class that will be use to instantiate the module. + <emphasis role="bold">class</emphasis> - Java class that will be use to instantiate the module. </para> </listitem> <listitem> @@ -754,7 +754,7 @@ <emphasis role="bold">name</emphasis> - property name. This value will be used to refer to the property in <emphasis>UserProfileModule</emphasis> </listitem> <listitem> - <emphasis role="bold">type</emphasis> - <trademark class="trade">Java</trademark> type of property. This type will be checked when in <emphasis>UserProfileModule</emphasis> + <emphasis role="bold">type</emphasis> - Java type of property. This type will be checked when in <emphasis>UserProfileModule</emphasis> methods invocation. </listitem> <listitem> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/portalapi.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/portalapi.xml 2008-06-13 00:24:24 UTC (rev 11010) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/portalapi.xml 2008-06-13 00:36:07 UTC (rev 11011) @@ -416,7 +416,7 @@ On this method we simply filter down to UserAuthenticationEvent then depending on the type of authentication event we update the counters. <emphasis>counter</emphasis> keeps track of the registered and logged-in users, while counterEver only counts the number of times people logged-in the portal.</para> - <para>Now that the <trademark class="trade">Java</trademark> class has been written we need to register it so that it can be called when the events are triggered. To do + <para>Now that the Java class has been written we need to register it so that it can be called when the events are triggered. To do so we need to register it as an MBean. It can be done by editing the sar descriptor file: <emphasis>YourService.sar/META-INF/jboss-service.xml</emphasis> so that it looks like the following: <programlisting><![CDATA[ Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-06-13 00:24:24 UTC (rev 11010) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-06-13 00:36:07 UTC (rev 11011) @@ -161,7 +161,7 @@ <sect3> <title>Portlet Classes</title> <para> - The following is the <filename>HelloWorldPortlet/src/main/org/jboss/portlet/hello/HelloWorldPortlet.java</filename> <trademark class="trade">Java</trademark> source file, which comes bundled with the <ulink + The following is the <filename>HelloWorldPortlet/src/main/org/jboss/portlet/hello/HelloWorldPortlet.java</filename> Java source file, which comes bundled with the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles...;: </para> <para>