commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CHAIN-63) Replace Context with Map<String, ? extends Object>
Date Tue, 10 Jan 2012 17:36:39 GMT

    [ https://issues.apache.org/jira/browse/CHAIN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183403#comment-13183403
] 

Simone Tripodi commented on CHAIN-63:
-------------------------------------

Don't worry, that is because you maybe misses some discussions in the dev@ ML - we agreed
on keeping the {{Context}} because users can still customize the context behavior, (put|get)
mrthods would not be enough for all situations.

Development is still on patch, there is a compilation issue discussed in CHAIN-58, if you're
interested on providing help you can apply the latest patch locally and try to fix the error
- remember that to be involved every kind of contribution is always much more than welcome!
:)
                
> Replace Context with Map<String, ? extends Object>
> --------------------------------------------------
>
>                 Key: CHAIN-63
>                 URL: https://issues.apache.org/jira/browse/CHAIN-63
>             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
required
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message