Am I correct in saying that this causes an issue when writing an application that runs both standalone and in a portal?
For example, if I have more than one portlet in my application which share data through the session, then I have to mark such managed-beans as application scope in JSF. However, if I use such a managed-bean in the stand-alone version, then all users would have access to the same data - yes?
Or am I actually looking at a 0.00001% chance use-case? I guess there's no problem if the application only uses one portlet.
Thanks,
D.
On 10/27/05, Stan Silvert <[EMAIL PROTECTED]> wrote:
Yes, this is required by the spec. See the javadoc for
ExternalContext.getSessionMap().
Stan Silvert
JBoss, Inc.
[EMAIL PROTECTED]
callto://stansilvert
> -----Original Message-----
> From: Henrik Bentel [mailto: [EMAIL PROTECTED]]
> Sent: Wednesday, October 26, 2005 6:28 PM
> To: [email protected]
> Subject: JSF/Myfaces and PorletSession PORTLET_SCOPE
>
> Hi
>
> After having some object scope issues with my JSF porlet on Liferay I
> snooped around
> org/apache/myfaces/context/portlet/PortletExternalContextImpl.java
> and org/apache/myfaces/context/portlet/SessionMap.java
>
> I notices that the SessionMap implementation only uses the portlet
> scope (PortletSession.PORTLET_SCOPE) when putting or retrieving
> objects from the PortletSession.
> It never uses the application scope( PortletSession.APPLICATION_SCOPE),
> which is usefull for portlet to portlet communication.
>
> I'm just curious if this is required by the JSF specification or just
> the obvious choice.
>
> thx,
> Henriki

