Portlet "global session scope" is unaccessible from JSF views [SWF-195]

[spring-operator]

Keith Garry Boyce opened SWF-195 and commented

Currently JSF provides support for accessing sessionScope and applicationScope natively, but provides no support for globalSessionScope applicable in a Portlet environment. Spring Web Flow provides this access through its ExternalContext abstraction, however, as of SWF 1.0.4 there is no way to access this data structure from a JSF view.

A workaround here would be to use Spring 2.0's custom bean scoping features to configure a bean sourced from global session scope. This ticket should investigate providing uniform access to the global session scope structure from a JSF view...

---

Original report:

Access could be provided like ${externalContext.sessionMap.foo} with an enhancement to FlowExecutionVariableResolver and FlowExecutionPropertyResolver.

However, is JSF's default support for resolving session and request scope variables is good enough? With Spring 2.0 as the managed bean provider and its custom scopes feature this might not be necessary as well. (Though this has the benefit of an explict prefix to reduce the likeihood of name clashes)

---

Affects: 1.0.4

Attachments:

• WebFlowPropertyResolver.java (6.42 kB)
• WebFlowVariableResolver.java (952 bytes)

[spring-operator]

Jeremy Grelle commented

"However, is JSF's default support for resolving session and request scope variables is good enough?"

I believe the answer is probably yes. You can already do this via JSF/EL's implicit objects. In other words, #{sessionScope.foo} and #{requestScope.foo} are already required to be supported in the JSF implementation.

[spring-operator]

Keith Garry Boyce commented

Where jsf falls short is to provide access to portlet session APPLICATION_SCOPE. There is no jsf mechanism to do this in a portlet agnostic way. This is why i'm asking for it. externalContext.globalSessionMap is the main driver.

[spring-operator]

Keith Donald commented

Reopening with a clarification.

[spring-operator]

Keith Donald commented

Possible now with #{externalContext.globalSessionMap.foo}