commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (Closed) (JIRA)" <>
Subject [jira] [Closed] (CHAIN-63) Replace Context with Map<String, ? extends Object>
Date Tue, 10 Jan 2012 16:37:39 GMT


Simone Tripodi closed CHAIN-63.

       Resolution: Duplicate
    Fix Version/s: 2.0
         Assignee: Simone Tripodi

This is a duplicate of CHAIN-58
> Replace Context with Map<String, ? extends Object>
> --------------------------------------------------
>                 Key: CHAIN-63
>                 URL:
>             Project: Commons Chain
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Ales Dolecek
>            Assignee: Simone Tripodi
>            Priority: Minor
>             Fix For: 2.0
> Hello,
>   I always wandered why you *force* chain users to use the Context interface which adds
nothing over Map. I would understand that if the Context would not inherit from map and only
> Object put(String, Object)
> Object get(String)
> But since Context itself IS Map then you gain nothing while disallowing use of Map implementations.
I know that sou suggest that Context shall implement "Attribute-Property Transparency" but
it is only recomendation and is not forced by commons chains anyway.
> And if you define execute like
> Object execute(Map<String, ? extends Object> context)
> it can still accept Context instances and all its subclasses.
> The downside is that you would have to give up the retrieve method introduced to Context.
And BTW the Context imposes hard restriction see my other bug.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message