Author: mmcallis Date: 2008-06-05 21:05:45 -0400 (Thu, 05 Jun 2008) New Revision: 10930 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/authentication.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/ldap.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/security.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml Log: fixing the case of certain Java trademarks Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/authentication.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/authentication.xml 2008-06-06 01:04:56 UTC (rev 10929) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/authentication.xml 2008-06-06 01:05:45 UTC (rev 10930) @@ -16,7 +16,7 @@ To better understand authentication mechanisms in JBoss Portal please refer to <link linkend="security.security_authentication">Security</link> chapter. To learn more about JAAS look for proper documentation on - <ulink url="http://java.sun.com/javase/6/docs/technotes/guides/security/&qu... security</ulink> website. + <ulink url="http://java.sun.com/javase/6/docs/technotes/guides/security/&qu... Security</ulink> website. To learn more about security in JBoss Application Server please read <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSX">JBoss... documentation. </para> 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-06 01:04:56 UTC (rev 10929) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-06-06 01:05:45 UTC (rev 10930) @@ -266,7 +266,7 @@ <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 systems, change into the <filename>$JBOSS_HOME/bin/</filename> directory and run the following command: + 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 systems, change into the <filename>$JBOSS_HOME/bin/</filename> directory and run the following command: </para> <para> <screen> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/ldap.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/ldap.xml 2008-06-06 01:04:56 UTC (rev 10929) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/ldap.xml 2008-06-06 01:05:45 UTC (rev 10930) @@ -154,7 +154,7 @@ </config> </datasource>]]></programlisting> <para> - Remember, as it is described in the <ulink url="http://java.sun.com/products/jndi/tutorial/ldap/connect/config.... documentation</ulink>, these options are system properties, not environment properties, and as such, they affect all connection pooling requests in the Java runtime. + Remember, as it is described in the <ulink url="http://java.sun.com/products/jndi/tutorial/ldap/connect/config.... documentation</ulink>, these options are system properties, not environment properties, and as such, they affect all connection pooling requests in the Java runtime environment. </para> </sect2> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/security.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/security.xml 2008-06-06 01:04:56 UTC (rev 10929) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/security.xml 2008-06-06 01:05:45 UTC (rev 10930) @@ -305,13 +305,7 @@ <sect1 id="security.security_authentication"> <title>Authentication with JBoss Portal</title> - <para>JBoss Portal relies on Java EE for the authentication of users. The Java EE authentication has its advantages - and drawbacks. The main motivation for using Java EE security is the integration with the application server and the - operational environment in which the portal is deployed. The servlet layer provides already the authentication functionality - and obviously it is not a responsibility of the portal. Whenever a user is authenticated by the servlet layer - its security identity is propagated throughout the call stack in the different layers of the Java EE stack. The weaknesses - are the lack of an explicit logout mechanism and the lack of dynamicity in the mapping of URL as security resources. However - JBoss Portal improves that behavior when it is possible to do so.</para> + <para>JBoss Portal relies on Java Platform, Enterprise Edition (Java EE) for the authentication of users. The Java EE authentication has its advantages and drawbacks. The main motivation for using Java EE security is the integration with the application server and the operational environment in which the portal is deployed. The servlet layer provides already the authentication functionality and obviously it is not a responsibility of the portal. Whenever a user is authenticated by the servlet layer its security identity is propagated throughout the call stack in the different layers of the Java EE stack. The weaknesses are the lack of an explicit logout mechanism and the lack of dynamicity in the mapping of URL as security resources. However JBoss Portal improves that behavior when it is possible to do so.</para> <sect2> <title>Authentication configuration</title> <para>JBoss Portal can be seen before all as a web application and therefore inherits all the configuration mechanisms 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-06 01:04:56 UTC (rev 10929) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-06-06 01:05:45 UTC (rev 10930) @@ -148,7 +148,7 @@ <sect3> <title>Package Structure</title> <para> - Like other Java EE applications, portlets are packaged in WAR files. A typical portlet WAR file can include servlets, resource bundles, images, HTML, JSPs, and other static or dynamic files. The following is an example of the directory structure of the HelloWorldPortlet portlet: + Like other Java Platform, Enterprise Edition (Java EE) applications, portlets are packaged in WAR files. A typical portlet WAR file can include servlets, resource bundles, images, HTML, JSPs, and other static or dynamic files. The following is an example of the directory structure of the HelloWorldPortlet portlet: </para> <para> <mediaobject>