I checked in a very, very temporary mechanism for accessing portlet artifacts and APIs for this release. This should not be relied upon in any way, shape, or form in future releases.

To access the PortletRequest, PortletConfig, and their associated APIs, you can do the following:

First, you need to get an attribute from the request that was placed there before the dispatch:

FacesContext fc = FacesContext.getCurrentInstance();
ExternalContext ec = fc.getExternalContext();
HttpServletRequest req = (HttpServletRequest)ec.getRequest();
Object obj = req.getAttribute(PortletArtifactHack.PORTLET_HACK_KEY);

The resulting object is an instance of PortletArtifactHack but it implements both PortletRequest and PortletConfig interfaces so you can cast it in any one of the following three ways depending on your requirements.

PortletArtifactHack hack = (PortletArtifactHack)obj;
PortletRequest portletRequest = (PortletRequest)obj;
PortletConfig portletConfig = (PortletConfig)obj;

Many of the methods throw UnsupportedOperationException()s. I've only exposed a few things that people need right away, like getPreferences().

This hack doesn't seem to work well due to the intricacies of the JSF lifecycle. We need to sit down and decide how we want to do this properly for 1.6.

Deryk,

Attached is is a simplified version of the PortletArtifactHack.java file that should do me well until you guys reach 1.7.

Thanks,

Neil

I've checked in the supplied file so that it will be there for the 1.6 release.

Marking as FIXED for 1.6. The current solution is completely temporary. A more comprehensive solution is required for the 1.7 release. A new case will be opened for that work.