We could perhaps set ourselves up for success in many situations. I like the idea of using ServiceLoader which is part of the JDK. All that means is that we include a file called META-INF/services/org.apache.commons.proxy.ProxyFactory and in it we have the implementation class name. Very low impact, so we should probably at least do that.
On Fri, Jul 16, 2010 at 6:55 PM, Matt Benson <[email protected]> wrote: > > On Jul 16, 2010, at 5:02 PM, James Carman wrote: > >> One of the other major requests I've had from folks is the >> "auto-discovery" mechanism. So, basically they just call one static >> method somewhere to obtain a ProxyFactory and based on what's on the >> classpath, we determine what they're talking about. Perhaps we can >> just add that into ProxyUtils? We could do something similar to what >> SLF4J does, or we could just simply use the service discovery >> mechanism built into the JDK? What do you think? >> > > Perhaps this is a naive question, but is there a reason not to use > [discovery]? Dog food tastes good. ;) > > -Matt > >> On Fri, Jul 16, 2010 at 5:58 PM, James Carman >> <[email protected]> wrote: >>> On Fri, Jul 16, 2010 at 5:48 PM, Matt Benson <[email protected]> wrote: >>>> Consider it done, then. :) >>>> >>>> Poor birds. >>>> >>> >>> Sorry, my wife has that "angry birds" application on her ipod touch, >>> so I've been on a bird killing spree for the past few weeks. >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
