Proxy design pattern

Question

Hey,
I have jar that run in different enviroments (client,server,partners).
In my jar i have some method that in case they called the action that executed is depend on the implementor.
For example let say that i have method "updateXXX(long id,String name){
Notify.notify(...)
if this called in the client than it need to lookup to this service and send the class name, method name and the method parameters to the service.
if it run in the server than it need to run XXX with the same parameters (this infrastrcture need to server some method with different parameters).
Is the proxy design patterns is the solution for this?
I thought to demand from each imlementor that want to use those kind of methods to implement a plugin with a given class name and in notify to load this class with class.forName, what are you say about this soultion?
any other ideas will be more than welcome.

Answer 1

The proxy pattern could help here, but isn't the simplest solution. You just want to define an interface that has those updateXXX methods declared on it, and have several classes implement those methods, such as one which executes some code in the same process, or one that does so over RMI, that sort of thing. Write your calling code against that interface, and configure at runtime which class they'll be calling
interface Updater {
    void updateXXX(Object params);
class LocalUpdater implements Updater {
     public void updateXXX(Object params) {
       // code to do work here
class RemoteUpdater implements Updater {
public void updateXXX(Object params) {
       // code to do remote work here
class Client {
   Updater myUpdater;
   Client(Updater updater) { // constructor takes an instance of something which implements Updater
       myUpdater = updater;
    void doSomething() {
       myUpdater.updateXXX("params"); // see how this class is decoupled from your Updater implementations
}How you inject your concrete dependencies is up to you.