Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <403413556.1221493665244.JavaMail.jira@brutus>
Date: Mon, 15 Sep 2008 08:47:45 -0700 (PDT)
From: "Pete Ford (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (CHAIN-45) Proposed code to allow decoupling of key
 names in contexts from key names used in Command code
In-Reply-To: <1542595052.1221493544357.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CHAIN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Ford updated CHAIN-45:
---------------------------

    Attachment: cx-commons-chain-mappedcommand.jar

JAR file containing sources - unpack to view the source files. The file also includes binaries, i.e. this file can be included in a classpath as-is.

> 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
>         Environment: Java environments
>            Reporter: Pete Ford
>            Priority: Minor
>         Attachments: cx-commons-chain-mappedcommand.jar
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.