Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 7 Apr 2014 16:12:19 +0000 (UTC)
From: "Matt Benson (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12407842.1225882567472.74009.1396887139013@arcas>
In-Reply-To: <JIRA.12407842.1225882567472@arcas>
References: <JIRA.12407842.1225882567472@arcas>
Subject: [jira] [Updated] (PROXY-14) Strategy-Based ObjectProvider
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Benson updated PROXY-14:
-----------------------------

    Fix Version/s: 2.x

> Strategy-Based ObjectProvider
> -----------------------------
>
>                 Key: PROXY-14
>                 URL: https://issues.apache.org/jira/browse/PROXY-14
>             Project: Commons Proxy
>          Issue Type: New Feature
>    Affects Versions: 1.0
>            Reporter: James Carman
>            Assignee: James Carman
>             Fix For: 2.x
>
>
> Implement a strategy-based ObjectProvider.  Basically, the provider would choose different strategy objects (that implement the service interface) based on information obtained at runtime during the method invocation.  One example would be a strategy-based provider which chose its strategy object based on the type of object passed in as one of the method parameters (similar to HiveMind's strategy support).  For example, suppose I have a service interface like:
> {code}
> public interface Renderer {
>   public void render(Shape shape);
> }
> {code}
> and I want to provide different implementations for Circle, Rectangle, Triangle, etc., then I would provide a mapping from those types to implementation objects that also implement Renderer.  Proxy would create a dynamic proxy that would choose which implementation object to use at runtime based on the type of shape passed in to the render method.


--
This message was sent by Atlassian JIRA
(v6.2#6252)