You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Benedikt Ritter (JIRA)" <ji...@apache.org> on 2013/07/04 21:33:48 UTC
[jira] [Updated] (CHAIN-45) Proposed code to allow decoupling of
key names in contexts from key names used in Command code
[ https://issues.apache.org/jira/browse/CHAIN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedikt Ritter updated CHAIN-45:
---------------------------------
Component/s: Base
> Proposed code to allow decoupling of key names in contexts from key names used in Command code
> ----------------------------------------------------------------------------------------------
>
> Key: CHAIN-45
> URL: https://issues.apache.org/jira/browse/CHAIN-45
> Project: Commons Chain
> Issue Type: New Feature
> Components: Base
> Environment: Java environments
> Reporter: Pete Ford
> Priority: Minor
> Attachments: cx-commons-chain-mappedcommand.jar, WhyThreadLocals.txt
>
>
> Command code typically refers to context values using fixed keys. This makes it difficult to create commands that are truly re-usable; it's often necessary to include commands to move values between keys so that the values are where the various commands expect them.
> The attached code allows command code to refer to keys using a "logical" name which is mapped at runtime to the actual keys to be used to access the context. The mapping between the logical and actual names is specified per command instance and is easily set up in a catalog XML file.
> The package also supports nested hierarchical contexts and allows contexts within a hierarchy to be logically mapped in a similar way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira