Bug 1040984 - Just Added page is missing in the sample-portal quickstart
Summary: Just Added page is missing in the sample-portal quickstart
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Quickstarts
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER01
: 6.1.1
Assignee: Peter Palaga
QA Contact: Dominik Pospisil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:18 UTC by Petr Mensik
Modified: 2015-07-20 01:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-17 11:00:27 UTC
Type: Bug


Attachments (Terms of Use)

Description Petr Mensik 2013-12-12 13:18:40 UTC
When you deploy sample-portal.ear into the $JBOSS_HOME/gatein/extension, then the Just Added page is not available under localhost:8080/portal/classic/page-just-added, there is also an error in localization showing "#{portal.extension.justAdde..." instead of Just Added.

Server log shows that the portlet is missing

org.gatein.pc.api.NoSuchPortletException: No such portlet /portal-extension.JustAddedPortlet

Comment 2 Peter Palaga 2013-12-17 11:00:27 UTC
Cannot reproduce on a fresh JBoss Portal 6.1.1.DR2 instance with corresponding quickstarts.

Firstly, the description of the issue seems to be a little bit confused: page-just-added and JustAddedPortlet are parts of portal-extension.ear. They are not included in sample portal as seems to be expected by the reporter.

Secondly, scenarios with sample-portal or portal-extension always need to be done on a clean portal installation. Esp. you cannot start the portal once with portal-extension.ear deployed, then remove portal-extension.ear and start the portal again. This issue seems to be a result of some such scenario.

Comment 3 Petr Mensik 2013-12-17 13:27:33 UTC
Ok, problem was caused by accidentally deploying portal-extension.ear instead of sample-portal.ear. So I checked it again and everything is working just fine. Sorry for confusion.


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