Hi Ed,
In a portlet environment, the FacesServlet is not invoked. Instead, the javax.portlet.faces.Bridge [1] implementation is responsible for receiving requests, running the JSF lifecycle, etc.
I'll let others comment on the suitability of creating the windowId in the FacesServlet for a servlet environment though.
Neil
[1]
http://myfaces.apache.org/portlet-bridge/2.0/api/apidocs/javax/portlet/faces/Bridge.html
On Feb 13, 2012, at 11:33 PM, Edward Burns wrote:
> Hello Experts,
>
> I've been discussing this issue on ##jsf but due to timezone issues I
> think it's best to take it asynchronous.
>
> My first order of business was to edit the proposal on the MYFACES wiki [1]
> so that I could use it as a starting point for writing the spec
> language. We made some progress with this, but it's still not where I
> need it to be so I can just sit down and write it out.
>
> Here are some questions I still have after reading the proposal in its
> current state:
>
> Q.2 aside from before RestoreView, what other pre-phase actions are required?
>
> Q.3 post-phase action is currently empty. What possible actions could
> there be here?
>
> Q.4 It seems like the right place to handle the creation of the windowId
> is in the FacesServlet. Why not there?
>
> I think Q.4 is the most pressing. Can someone answer me that one?
>
> Thanks,
>
> Ed
>
> [1] https://cwiki.apache.org/confluence/display/MYFACES/WindowId+Proposal
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | homepage: | http://ridingthecrest.com/