[gatein-commits] gatein SVN: r8870 - epp/docs/branches/5.2/Developer_Guide/en-US.

Author: ppenicka Date: 2012-10-11 15:03:37 -0400 (Thu, 11 Oct 2012) New Revision: 8870 Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml Log: Implemented changes required in BZ#813583. Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml 2012-10-11 19:03:11 UTC (rev 8869) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml 2012-10-11 19:03:37 UTC (rev 8870) @@ -59,11 +59,11 @@ </para> <para> - We do not provide additional recommendation to choose one database server over another as long as it is one of the certified environment. + We do not provide additional recommendations to choose one database server over another as long as it is one of the certified environments. </para> <para> - As said earlier, content is stored through a JCR API, RDBMS aren't a great fit to store large files and it is possible to configure eXo JCR to store such files in the filesystem instead of a database, whereas metadata about the files would still be stored into the database. Note that if the website is running on a cluster, the filesystem will need to be accessible from all the nodes and a NFS solution needs to be set up. For more details see the notion of "value storage" in the reference guide. + As said earlier, content is stored through a JCR API, RDBMS aren't a great fit to store large files and it is possible to configure eXo JCR to store such files in the filesystem instead of a database, whereas metadata about the files would still be stored in the database. Note that if the website is running on a cluster, the filesystem will need to be accessible from all the nodes and a NFS solution needs to be set up. For more details see the notion of "value storage" in the reference guide. </para> </section> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml 2012-10-11 19:03:11 UTC (rev 8869) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml 2012-10-11 19:03:37 UTC (rev 8870) @@ -7,13 +7,13 @@ <title>Portal containers</title> <para> - In a single instance (or cluster) of JBoss Enterprise Portal Platform, multiple portals can be running and share resources with other portals with two level of granularity: + In a single instance (or cluster) of JBoss Enterprise Portal Platform, multiple portals can be running and share resources with other portals with two levels of granularity: </para> <itemizedlist> <listitem> <para> - Portal Containers: A portal container can host multiple sites, and an JBoss Enterprise Portal Platform instance can host multiple portal containers + Portal Containers: A portal container can host multiple sites, and a JBoss Enterprise Portal Platform instance can host multiple portal containers </para> </listitem> @@ -25,11 +25,11 @@ </itemizedlist> <para> - The biggest granularity is what is called "Portal Containers". A Portal Container can host multiple "Sites". Those two components have a unique identifier that can be found in the default URL mapping according to the following scheme: <code> <ulink url="http://localhost:8080/"/> &lt;portalcontainer&gt;/&lt;site&gt; </code> + The biggest granularity is what is called "Portal Containers". A Portal Container can host multiple "Sites". Those two components have a unique identifier that can be found in the default URL mapping according to the following scheme: <code> <ulink url="http://localhost:8080/"/>&lt;portalcontainer&gt;/&lt;site&gt; </code> </para> <para> - When creating a website, it is possible to create a portal container from scratch or extend an existing one. It is then possible to extend the portal container which is accessed at <ulink url="http://localhost:8080/portal"/> on the out of the box solution, this is the recommended way. While running multiple portal containers is possible, it's usually better to keep those on separate installation. Note that multiple websites can run in a single portal container and share some services. + When creating a website, it is possible to create a portal container from scratch or extend an existing one. It is then possible to extend the portal container which is accessed at <ulink url="http://localhost:8080/portal"/> on the out of the box solution, this is the recommended way. While running multiple portal containers is possible, it's usually better to keep those on separate installations. Note that multiple websites can run in a single portal container and share some services. </para> <para> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml 2012-10-11 19:03:11 UTC (rev 8869) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml 2012-10-11 19:03:37 UTC (rev 8870) @@ -22,7 +22,7 @@ <title>Developing Gadgets</title> <para> - OpenSocial gadgets are made of standard HTML and javascript. The container offers an API, the documentation for which is available <ulink url="http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Ga... . + OpenSocial gadgets are made of standard HTML and JavaScript. The container offers an API, the documentation for which is available <ulink url="http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Ga... . </para> <para> @@ -39,7 +39,7 @@ <title>Portlet Development</title> <para> - JBoss Enterprise Portal interface is fully customized with applications called portlets. Application development can be done by using the plain Portlet specification JSR-286 (refer to the "Portlet Primer" chapter in the JBoss Enterprise Portal Platform Reference Guide for more information), but it is also possible to use the JBoss Portlet Bridge to write applications with JSF and/or RichFaces and/or Seam, (refer to the "Getting started with JBoss Portlet Bridge" chapter of the JBoss Enterprise Portal Platform Reference Guide). + JBoss Enterprise Portal interface is fully customized with applications called portlets. Application development can be done by using the plain Portlet specification JSR-286 (refer to the "Portlet Primer" chapter in the JBoss Enterprise Portal Platform Reference Guide for more information), but it is also possible to use the JBoss Portlet Bridge to write applications with JSF and/or RichFaces and/or Seam (refer to the "Getting started with JBoss Portlet Bridge" chapter of the JBoss Enterprise Portal Platform Reference Guide). </para> <para>