Bug 793528 (JBEPP-608) - Docs: Documentation issues in reference guide - section2
Summary: Docs: Documentation issues in reference guide - section2
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-608
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Documentation
Version: 5.1.0.ER03
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.GA
Assignee: Scott Mumford
QA Contact: ecs-bugs
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 17:39 UTC by mposolda
Modified: 2014-06-17 13:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-30 05:43:36 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-608 0 None None None Never

Description mposolda 2010-11-03 17:39:17 UTC
project_key: JBEPP

Some documentation issues related to docs at http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5/html/Reference_Guide/

12.2.2.2. Portlet Class has bad package. It has "org.jboss.portal.portlet.portlets" but should be "org.jboss.portal.portlet.samples"

14.2.1 - typo GadgetRegisteryService.xml - should be GadgetRegistryService.xml

14.2.1 - It's mentioned application webapp "GateInGadgets" but this application does not exist. Should be "eXoGadgets".

Section 14.2.2.2 There is mentioned:
These servers have to be on the same domain as the gadget server. You can configure the container in eXoGadgetServer:/WEB-INF/classes/containers/default/container.js. 
But I am seeing that directory eXoGadgetServer:/WEB-INF/classes/ is empty.

Comment 1 Thomas Heute 2010-11-12 08:45:14 UTC
Tentatively set for 5.1.0 CR01

Comment 2 Scott Mumford 2010-11-30 05:43:36 UTC
The Gadgets section of the Reference Guide has been removed.

These issues have been corrected however, in case it is reinstated in a future version.

Thanks Marek, Thomas


Note You need to log in before you can comment on or make changes to this bug.