Details
New Feature
Major
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
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #14565 | Fri Jul 27 14:30:16 MDT 2007 | deryk.sinotte | |
| Files Changed | ||||
DEL
/icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/http/portlet/PortletArtifactHack.java
ADD
/icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/http/portlet/PortletArtifactWrapper.java
|
| Field | Original Value | New Value |
|---|---|---|
| Assignee | User Deryk.sinotte [ deryk.sinotte ] |
| Fix Version/s | 1.7 [ 10080 ] | |
| Affects | [Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration] |
| Assignee | User Deryk.sinotte [ deryk.sinotte ] | Jack van Ooststroom [ jack.van.ooststroom ] |
| Fix Version/s | 1.7DR#1 [ 10100 ] | |
| Fix Version/s | 1.7 [ 10080 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
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.
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Summary | Expose JSR-168 Portlet API to portlet developers | Support JSR-168 Portlet API |
| Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
| Fix Version/s | 1.7 [ 10080 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Jack van Ooststroom [ jack.van.ooststroom ] |
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.