ICEfaces
  1. ICEfaces
  2. ICE-1935

Support JSR-168 Portlet API

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.6
          • Fix Version/s: 1.7DR#1, 1.7
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Portlet
          • Affects:
            Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

            Description

            Developers building portlets using ICEfaces need to access portlet artifacts and APIs via JSF mechanisms. For example, ExternalContext.getRequest() should return a PortletRequest rather than an HttpServletRequest. This case has been opened to cover work in that area.

              Activity

              Descending order - Click to sort in ascending order
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              Exposing the Portlet API to ICEfaces Portlet developers has been mainly focussed on PortletRequest (RenderRequest) and its affiliates (PortalContext, PortletMode, PortletSession, PortletContext, PortletPreferences and WindowState), and PortletConfig, as these are most likely the Portlet API classes to be used.

              The PortletConfig is still to be retrieved through the PortletArtifactWrapper as there currently is no defined standard for retrieving the PortletConfig in JSF. However, we should keep an eye on JSR-301 and consider writing a JSF Portlet Bridge adapter.

              There is an outstanding issue with the PortletRequest.isUserInRole(String) method which is mentioned in ICE-1674.

              Marking this one as FIXED.

              Show
              Jack Van Ooststroom added a comment - Exposing the Portlet API to ICEfaces Portlet developers has been mainly focussed on PortletRequest (RenderRequest) and its affiliates (PortalContext, PortletMode, PortletSession, PortletContext, PortletPreferences and WindowState), and PortletConfig, as these are most likely the Portlet API classes to be used. The PortletConfig is still to be retrieved through the PortletArtifactWrapper as there currently is no defined standard for retrieving the PortletConfig in JSF. However, we should keep an eye on JSR-301 and consider writing a JSF Portlet Bridge adapter. There is an outstanding issue with the PortletRequest.isUserInRole(String) method which is mentioned in ICE-1674 . Marking this one as FIXED.
              Hide
              Permalink
              Ken Fyten added a comment -

              Over to Jack for verification and resolution.

              Show
              Ken Fyten added a comment - Over to Jack for verification and resolution.
              Hide
              Permalink
              Deryk Sinotte added a comment -

              The main changes to the framework have been made to expose the Portlet API to developers. Next to need to test and verify that the API is working as expected.

              Show
              Deryk Sinotte added a comment - The main changes to the framework have been made to expose the Portlet API to developers. Next to need to test and verify that the API is working as expected.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Deryk Sinotte
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: