Uploaded image for project: 'Alfresco'
  1. Alfresco
  2. ALF-5770

Liferay 6 / DocLIb Portlet summary

    Details

      Attachments

        Issue Links

          Activity

          Hide
          mhatfield Mike Hatfield added a comment -

          Note: Liferay 6.0.5 CE out-of-the-box has a blocker bug for IE7 when adding portlets or managing layouts. See http://issues.liferay.com/browse/LPS-12974 for details.

          Show
          mhatfield Mike Hatfield added a comment - Note: Liferay 6.0.5 CE out-of-the-box has a blocker bug for IE7 when adding portlets or managing layouts. See http://issues.liferay.com/browse/LPS-12974 for details.
          Hide
          paulhussein Paul Hussein (Inactive) added a comment -

          All these tests seem to be against LR 6. We specified LR 5.2.3 against IE7

          Show
          paulhussein Paul Hussein (Inactive) added a comment - All these tests seem to be against LR 6. We specified LR 5.2.3 against IE7
          Hide
          paulhussein Paul Hussein (Inactive) added a comment -

          could you try again with this setting in portal

          1. Set this property for the portlet container implementation to use. The
          2. default implementation is the internal Liferay implementation and provides
          3. for the most features and best performance. The Sun implementation
          4. demonstrates how to plugin a different portlet container implementation.
          5. #portlet.container.impl=internal
            portlet.container.impl=sun

          Its true LR6 does not push that setting forward as its now supports JSR286 fully itself.

          However, our spec was against 5.2.3. Its a configurable option within 5.2.3 which a lot of people use including us. This option is the only way to get WSRP working within Liferay and has to be switched on otherwise WSRP is unusable.

          We will not be moving to LR6 immediately as we have concentrated on the Alfresco 3.3 migration which is now running in prod against Liferay 5.2.3.

          As I said our original spec was LR 5.2.3, its a valid option to have switched on and in the current state the portlet is not Fit For Purpose for us and its the last critical issue I can see that needs addressing.

          Show
          paulhussein Paul Hussein (Inactive) added a comment - could you try again with this setting in portal Set this property for the portlet container implementation to use. The default implementation is the internal Liferay implementation and provides for the most features and best performance. The Sun implementation demonstrates how to plugin a different portlet container implementation. #portlet.container.impl=internal portlet.container.impl=sun Its true LR6 does not push that setting forward as its now supports JSR286 fully itself. However, our spec was against 5.2.3. Its a configurable option within 5.2.3 which a lot of people use including us. This option is the only way to get WSRP working within Liferay and has to be switched on otherwise WSRP is unusable. We will not be moving to LR6 immediately as we have concentrated on the Alfresco 3.3 migration which is now running in prod against Liferay 5.2.3. As I said our original spec was LR 5.2.3, its a valid option to have switched on and in the current state the portlet is not Fit For Purpose for us and its the last critical issue I can see that needs addressing.
          Hide
          mhatfield Mike Hatfield added a comment -

          A problem was found and fixed when using the JSR 286 compatible container mode. I'm not sure how Paul is obtaining the share.war on this branch however. It's on the 3.3.1+ branch, 3.3.5, 3.4 and HEAD (3.4.c)

          All reported bugs that were closed as "Cannot Reproduce" have been re-tested on Liferay 5.2.3 in OpenPortal mode with IE7 and are still not reproducible.

          Show
          mhatfield Mike Hatfield added a comment - A problem was found and fixed when using the JSR 286 compatible container mode. I'm not sure how Paul is obtaining the share.war on this branch however. It's on the 3.3.1+ branch, 3.3.5, 3.4 and HEAD (3.4.c) All reported bugs that were closed as "Cannot Reproduce" have been re-tested on Liferay 5.2.3 in OpenPortal mode with IE7 and are still not reproducible.
          Hide
          adavis Alan Davis added a comment -

          Changed Fix Version to 3.4 from 3.4.1 as it is not possible to move issues into MNT that have sub tasks

          Show
          adavis Alan Davis added a comment - Changed Fix Version to 3.4 from 3.4.1 as it is not possible to move issues into MNT that have sub tasks

            People

            • Assignee:
              closedbugs Closed Bugs
              Reporter:
              mhatfield Mike Hatfield
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 1 hour, 30 minutes
                1d 1h 30m