[
https://issues.apache.org/jira/browse/CHAIN-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158919#comment-13158919
]
Elijah Zupancic commented on CHAIN-58:
--------------------------------------
Hi Simo,
In the uploaded changeset, Context is defined as <K,V>. However, Catalogs and
all of the other supporting libraries use <String, Object>. So, if a consumer
wanted to use chain in a custom manner where they have another class instead of
String, they could only as long as they did not use ContextBase, Catalogs,
Servlet / Portlet add-ons. I believe that is what we discussed in the mailing
list.
I'm having difficulty finding the email by Naill with his suggestion. I've only
found a single message from him and google has too much noise to be useful.
Thanks,
-Elijah
> Update Chain Context interface to use K,V generics
> --------------------------------------------------
>
> Key: CHAIN-58
> URL: https://issues.apache.org/jira/browse/CHAIN-58
> Project: Commons Chain
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Elijah Zupancic
> Fix For: 2.0
>
> Attachments: chain-58.diff
>
>
> As discussed in the mailing list, I am suggesting that we change the
> definition of Context from:
> {noformat}
> public interface Context extends Map<String, Object> {
> {noformat}
> to:
> {noformat}
> public interface Context<K, V> extends Map<K, V> {
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
