commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <ja...@carmanconsulting.com>
Subject RE: [proxy] vs proxytoys
Date Tue, 23 Aug 2005 20:45:09 GMT
I didn't understand what you meant by your question:

why do you call the methods "object" there?

What methods are you talking about?  Do you mean the getObject() method on
the ObjectProvider interface.  Well, I thought about that.  A provider isn't
a factory, because it doesn't necessarily create the object it's providing,
so I didn't name the method createObject().  I guess I could have called it
provideObject(), but I chose getObject() instead.  It could easily be
changed if anyone has any really strong feelings about it. 

-----Original Message-----
From: Joerg Hohwiller [mailto:joerg@j-hohwiller.de] 
Sent: Tuesday, August 23, 2005 4:21 PM
To: Jakarta Commons Developers List
Subject: Re: [proxy] vs proxytoys

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jörg Schaible wrote:
> Hi James,
Hi there,
> 
> can you tell me, what you are missing with proxytoys? You announced to
have 
> a closer look , but did not write anything further.
It seems to be true that proxytoys and "commons-proxy" are quite similar
animals. The API seems to differ slightly (esp. according to the
Invoker/MethodIntercepter)

http://svn.apache.org/repos/asf/jakarta/commons/sandbox/proxy/trunk/src/java
/org/apache/commons/proxy/ProxyFactory.java

http://proxytoys.codehaus.org/javadoc/com/thoughtworks/proxy/ProxyFactory.ht
ml

The important things are:
"commons-proxy" works on a javassist implementation and has interesting
goodies for various provider stategies:
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/proxy/trunk/src/java
/org/apache/commons/proxy/provider/

proxytoys has interesting goodies called "toys" (btw: why do you call
the methods "object" there?):
http://proxytoys.codehaus.org/javadoc/com/thoughtworks/proxy/toys/

Maybe it would be possible to bring both together, but it may start and
fall by the political classpath thingy. I personally would always trust
a classpath "org.apache.commons.proxy" more thant "com.*" (even
thoughtworks produced a lot of great stuff such as XStream).
On the other hand proxytoys might already be in use so changing the
classpath might not be an option.
However this one is not up to me.

Anyways if this issue is through and commons-proxy is still there,
I could offer help in mavenizing the project (both maven 1 and 2 if you
like) so you'd have some benefits in maintaining the according site, etc.
> 
> - Jörg
> 
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDC4U9mPuec2Dcv/8RAotaAJ41P9bstfE98HT7QQ4pEjOla+agAgCePHUa
3Q3HvkGB2oGzRLKMmAKBN8E=
=M6/o
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message