No, I don't.
I just want to add some specific roles for the portlet the user just clicked on.

Each portlet needs to have its own Identity containing a list of roles for that particular user and portlet.
Now having an identity object per portlet session comes out of the box.
My problem is that at the time I try to add the roles, FacesContext.getCurrentInstance() is null and PortalIdentity.isPortletPhase() returns false. So I can't access the principal and find out about the user name using Identity.

Also I notice that PortalIdentity overrides hasRole but not addRole.
So existing code from a standalone application may still add roles using the Identity object, but these roles are "lost" because when we try to read them back, the method hasRole will not find them when the application is a portlet.

I believe it would be nice to override addRole to either:
- Properly add roles to portal (as a complement of hasRole)
- or throw an UnsupportedOperationException so that existing code will fail, making it easy to know what's going on.

Richard

I looked at the Portlet Bridge code and found out what the problem is.

PortalIdenty extends the Seam Identity class and overrides the getPrincipal() methods as below:

 public Principal getPrincipal() {
 if (isPortletPhase()) {
 Principal bridgePrincipal = FacesContext.getCurrentInstance()
 .getExternalContext().getUserPrincipal();
 return bridgePrincipal;
 } else {
 return super.getPrincipal();
 }
 }

Yes regarding the roles, this is clearly not part of the spec.

Now regarding FacesContext.getCurrentInstance() being null, I believe this is due to the fact that the Session scoped component are
instanciated before the FacesContext is setup.

In org.jboss.portletbridge.AjaxPortletBridge, the doFacesRequest() methods calls
initRequest(request, response, Bridge.PortletPhase.ActionPhase) where the Session component will be instanciated.

Only after this, the code deals with the FacesContext.

Maybe windowState.restoreRequest(facesContext, true) needs to be called earlier? (I'm not quite sure this is what need to be fixed as I haven't looked deeper in the code yet).

I'm not sure what you mean by:

it would be even better to remove all JSF stuff, even Faces Servlet

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
 version="2.5">
 <display-name>uarp</display-name>

 <session-config>
 <session-timeout>15</session-timeout>
 </session-config>

 <!-- JSF -->
 <servlet>
 <servlet-name>Faces Servlet</servlet-name>
 <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
 <load-on-startup>1</load-on-startup>
 </servlet>
 <servlet-mapping>
 <servlet-name>Faces Servlet</servlet-name>
 <url-pattern>/faces/*</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>Faces Servlet</servlet-name>
 <url-pattern>*.seam</url-pattern>
 </servlet-mapping>

 <!-- Seam -->
 <listener>
 <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
 </listener>
 <servlet>
 <servlet-name>Seam Resource Servlet</servlet-name>
 <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>
 </servlet>
 <servlet-mapping>
 <servlet-name>Seam Resource Servlet</servlet-name>
 <url-pattern>/seam/resource/*</url-pattern>
 </servlet-mapping>
 <filter>
 <filter-name>Seam Filter</filter-name>
 <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>
 </filter>
 <filter-mapping>
 <filter-name>Seam Filter</filter-name>
 <servlet-name>Faces Servlet</servlet-name>
 <dispatcher>FORWARD</dispatcher>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>INCLUDE</dispatcher>
 </filter-mapping>
 <filter>
 <display-name>Ajax4jsf Filter</display-name>
 <filter-name>ajax4jsf</filter-name>
 <filter-class>org.ajax4jsf.Filter</filter-class>
 <init-param>
 <param-name>createTempFiles</param-name>
 <param-value>true</param-value>
 </init-param>
 </filter>
 <filter-mapping>
 <filter-name>ajax4jsf</filter-name>
 <servlet-name>Faces Servlet</servlet-name>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 <dispatcher>INCLUDE</dispatcher>
 </filter-mapping>

 <!-- Parameters -->

 <!-- Facelets -->
 <context-param>
 <param-name>facelets.DEVELOPMENT</param-name>
 <param-value>false</param-value>
 </context-param>
 <context-param>
 <param-name>facelets.SKIP_COMMENTS</param-name>
 <param-value>false</param-value>
 </context-param>

 <!-- JSF -->
 <context-param>
 <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
 <param-value>.xhtml</param-value>
 </context-param>
 <context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>server</param-value>
 </context-param>
 <context-param>
 <param-name>javax.portlet.faces.renderPolicy</param-name>
 <param-value>ALWAYS_DELEGATE</param-value>
 </context-param>

 <!-- RichFaces -->
 <context-param>
 <param-name>org.richfaces.SKIN</param-name>
 <param-value>blueSky</param-value>
 </context-param>
 <context-param>
 <param-name>org.richfaces.CONTROL_SKINNING</param-name>
 <param-value>enable</param-value>
 </context-param>
 <context-param>
 <param-name>org.richfaces.LoadStyleStrategy</param-name>
 <param-value>DEFAULT</param-value>
 </context-param>
 <context-param>
 <param-name>org.richfaces.LoadScriptStrategy</param-name>
 <param-value>NONE</param-value>
 </context-param>
 <context-param>
 <param-name>org.ajax4jsf.RESOURCE_URI_PREFIX</param-name>
 <param-value>rfRes</param-value>
 </context-param>
 <context-param>
 <param-name>org.ajax4jsf.COMPRESS_SCRIPT</param-name>
 <param-value>false</param-value>
 </context-param>
 <context-param>
 <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
 <param-value>org.jboss.portletbridge.application.FaceletPortletViewHandler</param-value>
 </context-param>

 <!-- PortletBridge -->
 <context-param>
 <param-name>org.jboss.portletbridge.ExceptionHandler</param-name>
 <param-value>org.jboss.portletbridge.SeamExceptionHandlerImpl</param-value>
 </context-param>

 <!-- The documentation says it is not needed, but it is! -->
 <context-param>
 <param-name>javax.faces.LIFECYCLE_ID</param-name>
 <param-value>SEAM_PORTLET</param-value>
 </context-param>

</web-app>

I got 1.0.0.SNAPSHOT but it doesn't seem your changes made it in yet. Is that correct?

This build didn't fix my problem and after reading again the previous posts, I believe we have a little misunderstanding :)

I have a Session scoped bean annotated @Startup (see first post)
The flow is the following:
- A user logs into the portal. Then MyApp portlet tab appears on the portal page.
- The user clicks on the portlet tab (at this point all the seam session scoped bean are instantiated when the AjaxPortletBridge.doFacesRequest(RenderRequest request, RenderResponse response) is called.

More precisely the following code is ran when the user clicks on the portlet tab:

public void doFacesRequest(RenderRequest request, RenderResponse response) throws BridgeException {
...
// Amongs other things, create the Seam Session Scoped beans
PortletBridgeContext bridgeContext = initRequest(request, wrappedResponse, Bridge.PortletPhase.RENDER_PHASE);
...
// Instantiate the facesContext
FacesContext facesContext = createFacesContext(request, wrappedResponse);
...
}

PortletBridgeContext initRequest(PortletRequest request, PortletResponse response, PortletPhase currentPhase) throws BridgeException {
...
// Create the Seam Session Scoped beans
PortletSession portletSession = request.getPortletSession();
...
}