Bug 793689 (JBEPP-765) - Docs: Broken link in JBoss Enterprise Portal Platform Reference Guide
Summary: Docs: Broken link in JBoss Enterprise Portal Platform Reference Guide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-765
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.1.GA,5.1.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.1.DEV01
Assignee: Scott Mumford
QA Contact: ecs-bugs
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks: JBEPP-801
TreeView+ depends on / blocked
 
Reported: 2010-12-22 00:50 UTC by Scott Mumford
Modified: 2014-06-17 13:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-15 07:03:32 UTC
Type: Task


Attachments (Terms of Use)


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

Description Scott Mumford 2010-12-22 00:50:02 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: JBEPP

In the EPP Reference Manual, section 13.4.6. Custom Ajax Error Handling , at http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.1/html/Reference_Guide/sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Custom_Ajax_Error_Handling.html .

"Read more about these settings here Request Errors and Session Expiration Handling ", but the link, http://docs.jboss.org/richfaces/3.3.3.BETA1/en/devguide/html/ArchitectureOverview.html#RequestErrorsAndSessionExpirationHandling , is broken (it gives a "404 Not Found" error).

(raised by David Lee Lambert dllamber.com)

Comment 1 Scott Mumford 2011-02-14 02:15:14 UTC
Link: Added: This issue is a dependency of JBEPP-801


Comment 2 Scott Mumford 2011-02-15 07:03:32 UTC
The url has been updated to point to the 3.3.3.FINAL version of the RichFaces guide, rather then the BETA1 version.

Comment 3 Scott Mumford 2011-08-09 01:20:48 UTC
Release Notes Docs Status: Added: Not Required



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