Details

      Description

      Just after install, I started to minimize every portlet on Welcome screen. For the first, after minimize, the restore button was shown (right behaviour). When I click on other portlet minimize button, the first portlet I minimized loose restore button, and in place appear a maximize button. So, appear that only can be one restore button at time! (only one restore button is allowed per page)

        Activity

        Hide
        Ate Douma added a comment -

        Closed again now properly recorded against Fix Version 2.1 as well

        Show
        Ate Douma added a comment - Closed again now properly recorded against Fix Version 2.1 as well
        Hide
        Scott T Weaver added a comment -

        Easy fix ever. The problem was the location of the DecoratorValve in the pipline.

        Standard pipline located in WEB-INF/assembly/pipelines.xml

        Broken:

        <bean id="jetspeed-pipeline"
        class="org.apache.jetspeed.pipeline.JetspeedPipeline"
        init-method="initialize"
        >
        <constructor-arg>
        <value>JetspeedPipeline</value>
        </constructor-arg>
        <constructor-arg>
        <list>
        <ref bean="capabilityValve"/>
        <ref bean="portalURLValve"/>
        <ref bean="securityValve"/>
        <ref bean="localizationValve"/>
        <ref bean="passwordCredentialValve"/>
        <ref bean="loginValidationValve"/>
        <ref bean="profilerValve"/>
        <ref bean="DecorationValve" />
        <ref bean="containerValve"/>
        <ref bean="actionValve"/>
        <ref bean="aggregatorValve"/>
        <ref bean="cleanUpValve"/>
        </list>
        </constructor-arg>
        </bean>

        Fixed:

        <bean id="jetspeed-pipeline"
        class="org.apache.jetspeed.pipeline.JetspeedPipeline"
        init-method="initialize"
        >
        <constructor-arg>
        <value>JetspeedPipeline</value>
        </constructor-arg>
        <constructor-arg>
        <list>
        <ref bean="capabilityValve"/>
        <ref bean="portalURLValve"/>
        <ref bean="securityValve"/>
        <ref bean="localizationValve"/>
        <ref bean="passwordCredentialValve"/>
        <ref bean="loginValidationValve"/>
        <ref bean="profilerValve"/>
        <ref bean="containerValve"/>
        <ref bean="actionValve"/>
        <ref bean="DecorationValve" />
        <ref bean="aggregatorValve"/>
        <ref bean="cleanUpValve"/>
        </list>
        </constructor-arg>
        </bean>

        Show
        Scott T Weaver added a comment - Easy fix ever. The problem was the location of the DecoratorValve in the pipline. Standard pipline located in WEB-INF/assembly/pipelines.xml Broken: <bean id="jetspeed-pipeline" class="org.apache.jetspeed.pipeline.JetspeedPipeline" init-method="initialize" > <constructor-arg> <value>JetspeedPipeline</value> </constructor-arg> <constructor-arg> <list> <ref bean="capabilityValve"/> <ref bean="portalURLValve"/> <ref bean="securityValve"/> <ref bean="localizationValve"/> <ref bean="passwordCredentialValve"/> <ref bean="loginValidationValve"/> <ref bean="profilerValve"/> <ref bean="DecorationValve" /> <ref bean="containerValve"/> <ref bean="actionValve"/> <ref bean="aggregatorValve"/> <ref bean="cleanUpValve"/> </list> </constructor-arg> </bean> Fixed: <bean id="jetspeed-pipeline" class="org.apache.jetspeed.pipeline.JetspeedPipeline" init-method="initialize" > <constructor-arg> <value>JetspeedPipeline</value> </constructor-arg> <constructor-arg> <list> <ref bean="capabilityValve"/> <ref bean="portalURLValve"/> <ref bean="securityValve"/> <ref bean="localizationValve"/> <ref bean="passwordCredentialValve"/> <ref bean="loginValidationValve"/> <ref bean="profilerValve"/> <ref bean="containerValve"/> <ref bean="actionValve"/> <ref bean="DecorationValve" /> <ref bean="aggregatorValve"/> <ref bean="cleanUpValve"/> </list> </constructor-arg> </bean>

          People

          • Assignee:
            Scott T Weaver
            Reporter:
            David Sean Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development