commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Benson (JIRA)" <>
Subject [jira] [Updated] (PROXY-14) Strategy-Based ObjectProvider
Date Mon, 07 Apr 2014 16:12:19 GMT


Matt Benson updated PROXY-14:

    Fix Version/s: 2.x

> Strategy-Based ObjectProvider
> -----------------------------
>                 Key: PROXY-14
>                 URL:
>             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
> {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

View raw message