Bug 793068 (JBEPP-150)

Summary:	Let a user reset an alias-binding by not defining it in a URL
Product:	[JBoss] JBoss Enterprise Portal Platform 4	Reporter:	Thomas Heute <theute>
Component:	unspecified	Assignee:	Thomas Heute <theute>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.0.GA_CP2	CC:	epp-bugs
Target Milestone:	---
Target Release:	4.3.0.GA_CP3
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-150
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-10 14:23:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Thomas Heute 2009-12-04 15:56:33 UTC

project_key: JBEPP

The behavior of alias-bindings isn't clearly defined and user may expect various cases.

We should make it configurable so that:

going to:
portal/page?binding1=1
then
portal/page?binding2=1

Actually reset binding1 if the user wants that behavior

and 
going to:
portal/page?binding1=1
then
portal/page?binding2=1

sets both values in default case so that it acts like any other public render parameters (such as set though a portlet)

Comment 1 Thomas Heute 2009-12-10 14:23:15 UTC

This is configurable in jboss-portals.sar/META-INF/jboss-service.xml
Default is:
   <mbean code="org.jboss.portal.core.model.portal.PortalObjectCommandFactory" name="portal:commandFactory=PortalObject"
          xmbean-dd="" xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
      <xmbean/>
      <depends optional-attribute-name="Mapper" proxy-type="attribute">
         portal:service=PortalObjectPathMapper,type=Default
      </depends>
      <attribute name="KeepPNState">true</attribute>
   </mbean>

Set KeepPNState to false to not keep the Public Navigational State across calls with alias bindings