[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014618#comment-13014618
]
Neil Griffin edited comment on PORTLETBRIDGE-208 at 4/1/11 2:37 PM:
--------------------------------------------------------------------
The current thinking is that the BridgeRequestScope interface will be defined
like this:
public interface BridgeRequestScope<K, V> extends ConcurrentMap<String, Object>
{
}
So the getAttribute/setAttribute would not be necessary since it extends
ConcurrentMap.
Closing this issue as WONTFIX
was (Author: ngriffin7a):
The current thinking is that the BridgeRequestScope interface will be
defined like this:
public interface BridgeRequestScope<String, Object> extends
ConcurrentMap<String, Object> {
}
So the getAttribute/setAttribute would not be necessary since it extends
ConcurrentMap.
Closing this issue as WONTFIX
> Proposal for 3.0 API: Expose attributes on BridgeRequestScope
> -------------------------------------------------------------
>
> Key: PORTLETBRIDGE-208
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-208
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 3.0.0
> Reporter: Neil Griffin
> Assignee: Michael Freedman
>
> It would be nice for the bridge implementation to be able to get/set various
> implementation-dependent attributes on the BridgeRequestScope, like the
> following method signatures:
> public interface BridgeRequestScope {
> ...
> Object getAttribute(String key);
> void setAttribute(String key, Object value);
> ...
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
