myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandr Smirnov (JIRA)" <>
Subject [jira] [Commented] (PORTLETBRIDGE-192) Proposal for 3.0 API: javax.portlet.faces.context.BridgeContext and associated BridgeContextFactory
Date Fri, 06 May 2011 19:04:03 GMT


Alexandr Smirnov commented on PORTLETBRIDGE-192:

Way, ther's a good point about BridgeConfig scope. I supposed that BridgeConfig should contain
per-portlet configuration, including portlet name, standard and extended options and so on.
Moving all of them into context seems as overkill.
So, we have three scopes of information: request scope, including portlet state, viewId, redirect
parameters and request type, portlet scoped : view portlet name, config, per-portlet options
and application-wide parameters.
I suggest to have different objects for every scope: BridgeContext for current request state,
BridgeConfig that's really contains current portlet configuration, and some for application-wide
options - BridgeApplicationConfig ?.
Ther are not a lot of options at application scope, so they could be put into BridgeConfig
P.S. In the Jboss bridge, BridgeImpl actually implements BridgeConfig interface tha's available
via custom BridgeContext.

> Proposal for 3.0 API: javax.portlet.faces.context.BridgeContext and associated BridgeContextFactory
> ---------------------------------------------------------------------------------------------------
>                 Key: PORTLETBRIDGE-192
>                 URL:
>             Project: MyFaces Portlet Bridge
>          Issue Type: New Feature
>          Components: General
>    Affects Versions: 3.0.0
>            Reporter: Neil Griffin
>            Assignee: Michael Freedman
> This class contains contextual information related to the bridge. It is inherently request
scoped, and is useful for sharing data between implementations of and
> Please refer to the following classes for this proposal: 

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message