Bug 812412

more issues:

p265: jcr-configuration.xml looks little bit different. needs fixing. same for p267

p291-292: again, the xml has changed a bit. i guess this is the current version:
http://anonsvn.jboss.org/repos/exo-jcr/jcr/tags/1.14.6-GA/exo.jcr.component.core/src/test/resources/conf/standalone/test-configuration-jbc.xml

the InitialContextInitializer is now <target-component> and i can't see any "default-context-factory" parameter in config files

p293-294: again the xml seems not to be updated. in http://anonsvn.jboss.org/repos/exo-jcr/jcr/tags/1.14.6-GA/exo.jcr.component.core/src/test/resources/conf/standalone/test-jcr-config-jbc.xml i can see, that the lock-manager is now configured in other way.

p301: text overlaping right edge of the page

p313: lock-config.xml for clustering mode has changed, some value have moved to properties and more (diff is needed). can be found in ..WEB-INF/conf/jcr/jbosscache/cluster/lock-config.xml
same for indexer-config.xml

p316: again in portal, the value was moved to property:
              <property name="jbosscache-configuration" value="${gatein.jcr.lock.cache.config}" />

in config from the exo jcr repo (above) the value is "conf/standalone/test-jbosscache-lock.xml"

p316-320: i can't find the ' test-jbosscache-lock-config.xml' file and the 'test-jbosscache-lock.xml' looks different than the example

p326: current version of jbosscache-indexer.xml file is missing the eviction tag

p345: values in table are overlapping

Ref.Guide comments:

main page
An in-depth guide to Enterprise Portal Platform 5.2.0
->
An in-depth guide to Enterprise Portal Platform 5.2.1

- update users on main page (remove Luc Texier, Wesley Hales and add new users who participate)

1.
based on the GateIn project which is the merge of two mature Java projects; JBoss Portal and eXo Portal
->
based on the GateIn project which is the merge of two mature Java projects: JBoss Portal and eXo Portal

6.1 last sentence
remove bold from "path"

6.2 after portal.xml
The defined classic portal is accessible to "Everyone" (at /portal/public/classic) but only members of the group /platform/administrators can edit it. 
->
The defined classic portal is accessible to "Everyone" (at /portal/classic) but only members of the group /platform/administrators can edit it. 

Subnodes
This element defines the parent/child relationship between a page and a subnode. 
->
This element defines the parent/child relationship between a node and a subnode. 

7.3.1 second image
- there is "daa" label on right node, but it should be called "bar" based on config file
(same for last image - overwrite mode)

Example 11.2. Example 2
/* >orientation=rt */
->
/* orientation=rt */

13.2.2. Building Controller
provide more insight into the routing engine (the findRoutes operation). see Rebuiding controller for more detail 
->
provide more insight into the routing engine (the findRoutes operation), see Rebuiding controller for more detail.

- remove next line with: > ReBuilding controller

Attribute configurationPath: the read only the configuration path of the controller xml file 
->
Attribute configurationPath: the read only configuration path of the controller xml file 

13.2.3.
- missing dots at last 2 sentences

13.3.1
The gtn:handler names is one the most important qualified name
->
The gtn:handler name is one the most important qualified name

An handler is a class
->
A handler is a class

Thanks for letting me know about these issues. I will address them in EPP 5.2.2 when I totally rework this user guide.

Some more comments regarding the Reference Guide:

14.2.1. Deploying your first portlet
- remove "or the jboss-epp-<VERSION>-docs/epp-doc/examples/portlets directory of the documentation package"

14.2.1.1. Compiling
- gatein-simplest-helloworld-5.2.0.GA.war -> gatein-simplest-helloworld-5.2.1.GA.war

14.2.1.3. Portlet Class
- Below is the Java source for an example portlet named simplesthelloworld/src/main/java/org/jboss/portal/portlet/samples -> Below is the Java source for an example portlet named SimplestHelloWorldPortlet

No. 1 should be rephrased: 
"The javax.portlet.Portlet interface uses the javax.portlet.GenericPortlet class which implements the Portlet render method to dispatch to abstract mode-specific methods. This makes it easier to support the standard portlet modes. Portlet render also provides a default implementation for the processAction, init and destroy methods."

- The interface does not "use" GenericPortlet class. Also I guess javax.portlet.GenericPortlet was supposed to be used instead of Portlet render in the last quoted sentence, that would make more sense. 

14.2.2. JavaServer Pages Portlet Example
- remove "or the /jboss-epp-<VERSION>-docs/epp-doc/examples/portlets directory of the documentation package"

- "Compiling the example" should be a numbered subsection (like its alternative in the previous section)

- jsphellouser/target/gatein-jsp-hellouser-5.2.0.GA.war -> jsphellouser/target/gatein-jsp-hellouser-5.2.1.GA.war

14.2.2.2. Portlet Class
- numbers in the code sample break the layout of the code, which is sort of hard to read as a result
- No. 4 in the first code sample is on a wrong line
- third code sample - numbers are not on the correct lines

14.2.2.4. JSF example using the JBoss Portlet Bridge
- 14.2.2.4. JSF example using the JBoss Portlet Bridge - should be a section higher by one level as the rest of the examples, i.e. 14.2.3.

- remove "or the /jboss-epp-<VERSION>-docs/epp-doc/examples/portlets directory of the documentation package"

Chapter 15. Shared portlet.xml
- "The file path is /<JBOSS_HOME>" - the initial "/" should be dropped

p204: text overlapping table
p215: i'm unable to grep PortalContainerConfig in the element <target-component> whern greping over exo JCR sources or portal config.
p222: "After deploying you find" -> "After deploying you can find". but deploying of what? i guess the file is always there.
p224: "HashTable The RootContainer creates a java HashTable". the 1st hashtable seems redundant. but the whole paragraph seems strange to me (like the question in the middle of it).
p237: for some paths the root is not clear. i.e. what is the root of portal/trunk/web/portal/src/main/webapp/WEB-INF/conf/database/database-configuration.tmpl.xml ?
p238-p242: again questions in the text.

16.1. JBoss Portlet Bridge Overview
- the disclaimer about JSR 329 not being final should be removed - the specification is already final

16.2.2. Bridge Frameworks and Extensions
- "JBoss Enterprise Portal Platform" should be highlighted as the rest of the technologies in the sentence

16.3.1.3.1. web.xml
- a confusing sentence - "Directs the bridge to first delegate the render only if an Exception is thrown then render the view based on its own logic." -> "Directs the bridge to first delegate the render and if and only if an exception is thrown, then render the view based on its own logic."

16.3.2.1. web.xml
- wrong configuration in the second code sample

<script src="/faces/rfRes/org/ajax4jsf/framework.pack.js" type="text/javascript"></script>
<script src="/faces/rfRes/org/richfaces/ui.pack.js" type="text/javascript"></script>
<link rel="stylesheet" type="text/css" href="/faces/rfRes/org/richfaces/skin.xcss"/>

should be changed to

<script src="/richFacesPortlet/faces/rfRes/org/ajax4jsf/framework.pack.js" type="text/javascript"></script>
<script src="/richFacesPortlet/faces/rfRes/org/richfaces/ui.pack.js" type="text/javascript"></script>
<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/>

i.e. the name of the portlet (war file) should be added to the path. It should be also noted in the description that the string "richFacesPortlet" comes from there.

16.3.2.2. Configuration needed for Richfaces to work with WSRP and PortletBridge
- "Richfaces" -> "RichFaces" (in the title)

- "The styles below must also be manually added to the facelets template header in the JBOSS_HOME/portletbridge/examples/richFacesPortlet-<VERSION>.war:richFacesPortlet.war/templates/main.xhtml file." -> "The styles below must also be manually added to the facelets template header (example from richFacesPortlet.war/templates/main.xhtml in JBOSS_HOME/portletbridge/examples/)."

- errors in the second code sample

<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfResorg/richfaces/renderkit/html/css/basic_both.xcss"/>
<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfResorg/richfaces/renderkit/html/css/extended_both.xcss"/>
<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/>

should be changed to

<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfRes/org/richfaces/renderkit/html/css/basic_both.xcss"/>
<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfRes/org/richfaces/renderkit/html/css/extended_both.xcss"/>
<link rel="stylesheet" type="text/css" href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/>

16.3.4.2.1. Configuration
- link should be changed to point to the current version of the bridge
"A clear and working example can be found in the Seam Booking Demo portlet. http://anonsvn.jboss.org/repos/portletbridge/tags/2.2.0.GA.EPP520/examples/seam/booking/" -> "A clear and working example can be found in the Seam Booking Demo (http://anonsvn.jboss.org/repos/portletbridge/tags/2.3.0.CP01.EPP521/examples/seam/booking/)."

16.3.4.3.1. Configuration
- ResourceBean.java link should point to the current tag of the bridge
http://anonsvn.jboss.org/repos/portletbridge/tags/2.0.0.CR1/examples/richfaces/richfaces-demo/src/main/java/org/richfaces/demo/common/ResourceBean.java -> http://anonsvn.jboss.org/repos/portletbridge/tags/2.3.0.CP01.EPP521/examples/richfaces/richfaces-demo/src/main/java/org/richfaces/demo/common/ResourceBean.java

- "url served from the portlets web application" -> "URL served from the portlet application"

16.4.1. Excluding Attributes from the Bridge Request Scope
- "any attribute beginning with foo.baz(wild-card)" -> "any attribute beginning with foo.baz."

Thanks for the cover to cover review Viliam, Miroslav, and Michal.

All general formatting issues identified are cause predominantly by FOP and will be fixed when Publican 3 stops using FOP for PDF transformation. wkhtmltopdf is the default engine in Publican 3 for PDF, and is streets ahead of crappy FOP. 

I will incorporate the errors in text as prescribed.

While the Reference Guide will not be converted cover-to-cover to task-based format, those changes surrounding your fixes may be tweaked slightly as part of continuous improvement.

(In reply to comment #0)
> taken from the pdf:
> http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.2/pdf/
> Reference_Guide/JBoss_Enterprise_Portal_Platform-5.2-Reference_Guide-en-US.
> pdf
> 
> p10: in the example on bottom of the page the #4 is outside the border and
> the last line is blue instead of black. the color is blue on the p11, too.
> p14-p16: the color of the ".png" extension is green and should be black.
> p22: this page is blank on a purpose?
> p110: the login dialogue now has the EPP letters in it and is red.
> p116: the URL link has another style than other URLs in the doc. maybe it
> would be nice to have all the http[s]:// links clickable in the doc.
> p156: ID_HOME would be nicer bold in the note on the top of the page.
> p157: cells in table 17.2 are overlapping

Corrected the Login dialog picture on PDF page 110. 

URLs will be normalized to <ulink> elements as I do more work on this guide.

(In reply to comment #1)

Thanks for your comments Viliam. PDF page numbers are not the best mechanism to reference issues by, because page numbers can change between releases. Please reference the closest block element heading you can, like I've done in my responses and questions. Chapter and Sections headings are great. Procedure titles are even better.

It helps me out heaps if you can do it like that. :D

> more issues:
> 
> p265: jcr-configuration.xml looks little bit different. needs fixing. same
> for p267
> 
> p291-292: again, the xml has changed a bit. i guess this is the current
> version:
> http://anonsvn.jboss.org/repos/exo-jcr/jcr/tags/1.14.6-GA/exo.jcr.component.
> core/src/test/resources/conf/standalone/test-configuration-jbc.xml
> 
> the InitialContextInitializer is now <target-component> and i can't see any
> "default-context-factory" parameter in config files

22.1. Portal configuration - XML changed as prescribed.

> 
> p293-294: again the xml seems not to be updated. in
> http://anonsvn.jboss.org/repos/exo-jcr/jcr/tags/1.14.6-GA/exo.jcr.component.
> core/src/test/resources/conf/standalone/test-jcr-config-jbc.xml i can see,
> that the lock-manager is now configured in other way.

25.2. Multi-database Configuration - XML changed as prescribed.

> 
> p301: text overlaping right edge of the page

FOP issue. Can not fix.

> 
> p313: lock-config.xml for clustering mode has changed, some value have moved
> to properties and more (diff is needed). can be found in
> ..WEB-INF/conf/jcr/jbosscache/cluster/lock-config.xml
> same for indexer-config.xml

30.4.2. Lock manager template - XML changed as prescribed.

30.4.3. Query handler (indexer) template - XML changed as prescribed

> p316: again in portal, the value was moved to property:
>               <property name="jbosscache-configuration"
> value="${gatein.jcr.lock.cache.config}" />
> 
> in config from the exo jcr repo (above) the value is
> "conf/standalone/test-jbosscache-lock.xml"

I can't match your feedback to the correct section to change. PDF page 316 is now the tail end of the code sample in 30.4.3. Query handler (indexer) template. Could you please re-confirm.

> 
> p316-320: i can't find the ' test-jbosscache-lock-config.xml' file and the
> 'test-jbosscache-lock.xml' looks different than the example

Not quite sure what I should do here. Do you know of another file that might replace test-jbosscache-lock-config.xml?

> 
> p326: current version of jbosscache-indexer.xml file is missing the eviction
> tag

Are you referring to 32.2.2. Cluster-ready indexing and the code samples in there. Which one in particular?

> 
> p345: values in table are overlapping

(In reply to comment #1)

Thanks for your comments Viliam. PDF page numbers are not the best mechanism to reference issues by, because page numbers can change between releases. Please reference the closest block element heading you can, like I've done in my responses and questions. Chapter and Sections headings are great. Procedure titles are even better.

It helps me out heaps if you can do it like that. :D

> more issues:
> 
> p265: jcr-configuration.xml looks little bit different. needs fixing. same
> for p267
> 
> p291-292: again, the xml has changed a bit. i guess this is the current
> version:
> http://anonsvn.jboss.org/repos/exo-jcr/jcr/tags/1.14.6-GA/exo.jcr.component.
> core/src/test/resources/conf/standalone/test-configuration-jbc.xml
> 
> the InitialContextInitializer is now <target-component> and i can't see any
> "default-context-factory" parameter in config files

22.1. Portal configuration - XML changed as prescribed.

> 
> p293-294: again the xml seems not to be updated. in
> http://anonsvn.jboss.org/repos/exo-jcr/jcr/tags/1.14.6-GA/exo.jcr.component.
> core/src/test/resources/conf/standalone/test-jcr-config-jbc.xml i can see,
> that the lock-manager is now configured in other way.

25.2. Multi-database Configuration - XML changed as prescribed.

> 
> p301: text overlaping right edge of the page

FOP issue. Can not fix.

> 
> p313: lock-config.xml for clustering mode has changed, some value have moved
> to properties and more (diff is needed). can be found in
> ..WEB-INF/conf/jcr/jbosscache/cluster/lock-config.xml
> same for indexer-config.xml

30.4.2. Lock manager template - XML changed as prescribed.

30.4.3. Query handler (indexer) template - XML changed as prescribed

> p316: again in portal, the value was moved to property:
>               <property name="jbosscache-configuration"
> value="${gatein.jcr.lock.cache.config}" />
> 
> in config from the exo jcr repo (above) the value is
> "conf/standalone/test-jbosscache-lock.xml"

I can't match your feedback to the correct section to change. PDF page 316 is now the tail end of the code sample in 30.4.3. Query handler (indexer) template. Could you please re-confirm.

> 
> p316-320: i can't find the ' test-jbosscache-lock-config.xml' file and the
> 'test-jbosscache-lock.xml' looks different than the example

Not quite sure what I should do here. Do you know of another file that might replace test-jbosscache-lock-config.xml?

> 
> p326: current version of jbosscache-indexer.xml file is missing the eviction
> tag

Are you referring to 32.2.2. Cluster-ready indexing and the code samples in there. Which one in particular?

> 
> p345: values in table are overlapping

FOP issue. Can not fix.

(In reply to comment #2)
> Ref.Guide comments:
> 
> main page
> An in-depth guide to Enterprise Portal Platform 5.2.0
> ->
> An in-depth guide to Enterprise Portal Platform 5.2.1

Changed to 5.2 generically, and added "and its patch releases" to cater for 5.2.x releases.

> 
> - update users on main page (remove Luc Texier, Wesley Hales and add new
> users who participate)

Removed users. Will add more as directed.

> 
> 1.
> based on the GateIn project which is the merge of two mature Java projects;
> JBoss Portal and eXo Portal
> ->
> based on the GateIn project which is the merge of two mature Java projects:
> JBoss Portal and eXo Portal

Changed to:

JBoss Enterprise Portal Platform is based on the GateIn project, which is the merge of two mature Java projects: JBoss Portal and eXo Portal.

> 
> 6.1 last sentence
> remove bold from "path"

That is correctly marked-up in XML as <filename>, which it is. That formats as bold. Leaving as is.

> 
> 6.2 after portal.xml
> The defined classic portal is accessible to "Everyone" (at
> /portal/public/classic) but only members of the group
> /platform/administrators can edit it. 
> ->
> The defined classic portal is accessible to "Everyone" (at /portal/classic)
> but only members of the group /platform/administrators can edit it. 

In the "Portal Navigation" section - Incorporated.

> 
> Subnodes
> This element defines the parent/child relationship between a page and a
> subnode. 
> ->
> This element defines the parent/child relationship between a node and a
> subnode. 

In the "Portal Navigation" section - Incorporated.

> 
> 7.3.1 second image
> - there is "daa" label on right node, but it should be called "bar" based on
> config file
> (same for last image - overwrite mode)

In section "Navigation Data" - TODO RAISE BUGZILLA SEPARATE TO THIS ONE TO WORK ON FIXING THESE ISSUES.

> 
> Example 11.2. Example 2
> /* >orientation=rt */
> ->
> /* orientation=rt */

Fixed. Docs QE: Search for surrounding text "   In this example we need to modify the padding according to the orientation:"

> 
> 13.2.2. Building Controller
> provide more insight into the routing engine (the findRoutes operation). see
> Rebuiding controller for more detail 
> ->
> provide more insight into the routing engine (the findRoutes operation), see
> Rebuiding controller for more detail.
> 
> - remove next line with: > ReBuilding controller

Removed the bullet point. Docs QE, search for "changed and reloaded at runtime, this helps the testing of different configurations easily" for surrounding text verification.

> 
> Attribute configurationPath: the read only the configuration path of the
> controller xml file 
> ->
> Attribute configurationPath: the read only configuration path of the
> controller xml file 

Deleted the extra "the".

> 
> 13.2.3. Controller Configuration (controller.xml)
> - missing dots at last 2 sentences

Added colons and full-stops. Also added the three types of parameters missing from the last sentence in this section. 

> 
> 13.3.1 Routing
> The gtn:handler names is one the most important qualified name
> ->
> The gtn:handler name is one the most important qualified name
> 
> An handler is a class
> ->
> A handler is a class

Fixed both instances.

(In reply to comment #4)
> Some more comments regarding the Reference Guide:
> 
> 14.2.1. Deploying your first portlet
> - remove "or the jboss-epp-<VERSION>-docs/epp-doc/examples/portlets
> directory of the documentation package"

Removed.

> 
> 14.2.1.1. Compiling
> - gatein-simplest-helloworld-5.2.0.GA.war ->
> gatein-simplest-helloworld-5.2.1.GA.war

Updated entity controlling this value.

> 
> 14.2.1.3. Portlet Class
> - Below is the Java source for an example portlet named
> simplesthelloworld/src/main/java/org/jboss/portal/portlet/samples -> Below
> is the Java source for an example portlet named SimplestHelloWorldPortlet

Changed as prescribed.

> 
> No. 1 should be rephrased: 
> "The javax.portlet.Portlet interface uses the javax.portlet.GenericPortlet
> class which implements the Portlet render method to dispatch to abstract
> mode-specific methods. This makes it easier to support the standard portlet
> modes. Portlet render also provides a default implementation for the
> processAction, init and destroy methods."
> 
> - The interface does not "use" GenericPortlet class. Also I guess
> javax.portlet.GenericPortlet was supposed to be used instead of Portlet
> render in the last quoted sentence, that would make more sense. 

Based on info in http://www.bluesunrise.com/portlet-api/javax/portlet/GenericPortlet.html, 
I've reworded the point. Please review for accuracy.

> 
> 14.2.2. JavaServer Pages Portlet Example
> - remove "or the /jboss-epp-<VERSION>-docs/epp-doc/examples/portlets
> directory of the documentation package"

Removed.

> 
> - "Compiling the example" should be a numbered subsection (like its
> alternative in the previous section)

Reworked, and fixed.

> 
> - jsphellouser/target/gatein-jsp-hellouser-5.2.0.GA.war ->
> jsphellouser/target/gatein-jsp-hellouser-5.2.1.GA.war

Fixed.

> 
> 14.2.2.2. Portlet Class
> - numbers in the code sample break the layout of the code, which is sort of
> hard to read as a result
> - No. 4 in the first code sample is on a wrong line
> - third code sample - numbers are not on the correct lines

I've done away completely with the <programlistingco> for these code samples.
Converted them to examples, standard <programlisting> entries, and used Java comments to highlight
the correct parts of the example. Let me know if this will cause issues if people copy-paste.
I don't know of any other way of correcting line callouts specifically, apart from this solution.

> 
> 14.2.2.4. JSF example using the JBoss Portlet Bridge
> - 14.2.2.4. JSF example using the JBoss Portlet Bridge - should be a section
> higher by one level as the rest of the examples, i.e. 14.2.3.

Promoted one section higher.

> 
> - remove "or the /jboss-epp-<VERSION>-docs/epp-doc/examples/portlets
> directory of the documentation package"
> 
> Chapter 15. Shared portlet.xml
> - "The file path is /<JBOSS_HOME>" - the initial "/" should be dropped

Fixed.

(In reply to comment #5)
> p204: text overlapping table

Manually broke classname with a space.

> p215: i'm unable to grep PortalContainerConfig in the element
> <target-component> whern greping over exo JCR sources or portal config.

NEEDINFO: Who would I ask to determine the corect XML config in this section (which for Docs QE happens to be 19.3.5.1.1. AddDependencies)

> p222: "After deploying you find" -> "After deploying you can find". but
> deploying of what? i guess the file is always there.

I've reworked this paragraph, and marked up the elements that were just formatted as words (they got lost in the text). Docs QE, search for "All custom configuration is made in the". The change is in the "Components" section.

> p224: "HashTable The RootContainer creates a java HashTable". the 1st
> hashtable seems redundant. but the whole paragraph seems strange to me (like
> the question in the middle of it).

I've removed the redundant text. This whole chapter needs to be reworked. It's a mess, from an information structure perspective.

NEEDINFO This seciton refers to exo-tomcat/exo-conf.  I don't know whether this is suggesting it only applies to stand-alone, non-supported versions. Can you make sense of it.

> p237: for some paths the root is not clear. i.e. what is the root of
> portal/trunk/web/portal/src/main/webapp/WEB-INF/conf/database/database-
> configuration.tmpl.xml ?
> p238-p242: again questions in the text.

I need to go through this guide and check all paths are correct. Many are not absolute paths. Making another ticket for this, as it will be a big job. I'll need to download the platform and unpack it so I can verify the paths.

TODO Make BZ to validate all paths in document.

(In reply to comment #6)
> 16.1. JBoss Portlet Bridge Overview
> - the disclaimer about JSR 329 not being final should be removed - the
> specification is already final

Removed Disclaimer.

> 
> 16.2.2. Bridge Frameworks and Extensions
> - "JBoss Enterprise Portal Platform" should be highlighted as the rest of
> the technologies in the sentence

Done.

> 
> 16.3.1.3.1. web.xml
> - a confusing sentence - "Directs the bridge to first delegate the render
> only if an Exception is thrown then render the view based on its own logic."
> -> "Directs the bridge to first delegate the render and if and only if an
> exception is thrown, then render the view based on its own logic."

Changed to "Directs the bridge to first delegate the render. If an exception is thrown, the bridge renders the view based on its own logic."

> 
> 16.3.2.1. web.xml
> - wrong configuration in the second code sample
> 
> <script src="/faces/rfRes/org/ajax4jsf/framework.pack.js"
> type="text/javascript"></script>
> <script src="/faces/rfRes/org/richfaces/ui.pack.js"
> type="text/javascript"></script>
> <link rel="stylesheet" type="text/css"
> href="/faces/rfRes/org/richfaces/skin.xcss"/>
> 
> should be changed to
> 
> <script src="/richFacesPortlet/faces/rfRes/org/ajax4jsf/framework.pack.js"
> type="text/javascript"></script>
> <script src="/richFacesPortlet/faces/rfRes/org/richfaces/ui.pack.js"
> type="text/javascript"></script>
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/>
> 
> i.e. the name of the portlet (war file) should be added to the path. It
> should be also noted in the description that the string "richFacesPortlet"
> comes from there.

Understood. I have made the distinction that "richFacesPortlet" is replaceable text and should be appropriately substituted.

> 
> 16.3.2.2. Configuration needed for Richfaces to work with WSRP and
> PortletBridge
> - "Richfaces" -> "RichFaces" (in the title)

Changed title to active voice "Configure RichFaces to work with WSRP and PortletBridge", which flows on to the next feedback item below.

> 
> - "The styles below must also be manually added to the facelets template
> header in the
> JBOSS_HOME/portletbridge/examples/richFacesPortlet-<VERSION>.war:
> richFacesPortlet.war/templates/main.xhtml file." -> "The styles below must
> also be manually added to the facelets template header (example from
> richFacesPortlet.war/templates/main.xhtml in
> JBOSS_HOME/portletbridge/examples/)."
> 
> - errors in the second code sample
> 
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfResorg/richfaces/renderkit/html/css/
> basic_both.xcss"/>
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfResorg/richfaces/renderkit/html/css/
> extended_both.xcss"/>
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/>
> 
> should be changed to
> 
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfRes/org/richfaces/renderkit/html/css/
> basic_both.xcss"/>
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfRes/org/richfaces/renderkit/html/css/
> extended_both.xcss"/>
> <link rel="stylesheet" type="text/css"
> href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/>

Changed as prescribed.

> 
> 16.3.4.2.1. Configuration
> - link should be changed to point to the current version of the bridge
> "A clear and working example can be found in the Seam Booking Demo portlet.
> http://anonsvn.jboss.org/repos/portletbridge/tags/2.2.0.GA.EPP520/examples/
> seam/booking/" -> "A clear and working example can be found in the Seam
> Booking Demo
> (http://anonsvn.jboss.org/repos/portletbridge/tags/2.3.0.CP01.EPP521/
> examples/seam/booking/)."

Updated as prescribed.

> 
> 16.3.4.3.1. Configuration
> - ResourceBean.java link should point to the current tag of the bridge
> http://anonsvn.jboss.org/repos/portletbridge/tags/2.0.0.CR1/examples/
> richfaces/richfaces-demo/src/main/java/org/richfaces/demo/common/
> ResourceBean.java ->
> http://anonsvn.jboss.org/repos/portletbridge/tags/2.3.0.CP01.EPP521/examples/richfaces/richfaces-demo/src/main/java/org/richfaces/demo/common/ResourceBean.java

Changed as prescribed.

> 
> - "url served from the portlets web application" -> "URL served from the
> portlet application"

Changed as prescribed.

> 
> 16.4.1. Excluding Attributes from the Bridge Request Scope
> - "any attribute beginning with foo.baz(wild-card)" -> "any attribute
> beginning with foo.baz."

Added separating dot.

Package: 

JBoss_Enterprise_Portal_Platform-Reference_Guide-5.2-web-en-US-5.2.2-6.el6eng

Link: 

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.2/html-single/Reference_Guide/index.html

Changelog:

* Tue Jul 10 2012 Jared Morgan <> - 5.2.2-6
- BZ#812412 - Extensive peer review comments incorporated. Book-wide spell-check run.

Remarks: 

Stage email received, and should appear shortly.

Incorporations start at Comment#8. Docs QE, if you see a NEEDINFO, or TODO, they are notes for me and require no review by you guys. Treat those fixes as "coming in a future version".

Also note that because FOP is causing this book to not built, I have disabled PDF builds during development phase. When Publican 3 is released, I will restage the book with PDF builds enabled. 

Most text overrun issues and display and presentation issues identified by the devs were because of FOP, so these have been annotated as appropriate.

Deferring this until we decide to release a new version of EPP 5.2.