Hide Forgot
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)
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