Comments on: Snippet: Automatic Proxy Creation in Clojure

By: Automatically create wrapper object in Clojure | LispCast

Automatically create wrapper object in Clojure | LispCast — Fri, 26 Mar 2010 14:38:36 +0000

[...] Brool shared a macro for creating a proxy that doesn’t throw exceptions for methods that aren’t define. It is called autoproxy. I [...]

By: Jetpack

Jetpack — Tue, 09 Mar 2010 13:24:55 +0000

Got the solution from #clojure: the extended class name needs to be put at the front of the interfaces argument of the macro. works like a charm.

Again, in my opinion this macro would be a very useful addition to clojure-contrib or core.

By: Jetpack

Jetpack — Tue, 09 Mar 2010 13:11:15 +0000

Tim, I’m trying to extend a class as well as implement an interface in the same proxy. Would you have an idea how I could do this with your auto-proxy macro? Simply adding the extended class to the auto-proxy arguments gives me an excpetion: “java.lang.IncompatibleClassChangeError: Implementing class”.

By: tim

tim — Fri, 15 Jan 2010 16:28:27 +0000

@Jetpack: Yah, I’d be interested in that, but last time I looked it wasn’t obvious how to go about submitting stuff. I’ll definitely take a look.

By: Jetpack

Jetpack — Mon, 04 Jan 2010 15:14:02 +0000

Tim, this is a very useful macro for me and I bet for plenty of others that want to migrate from Java to Clojure. Have you submitted it to Rich for inclusion in clojure-contrib or core?

By: tim

tim — Sun, 23 Aug 2009 20:10:38 +0000

@Duncan: I didn’t want it to throw an exception, I wanted it to just have an empty default implementation. Since it was being invoked as a callback from the API, I didn’t even have an intervening level in which I could put a try statement.

By: Duncan

Duncan — Sun, 23 Aug 2009 16:14:51 +0000

Why do you need to do this, doesn’t the proxy form already do this for you?

“If a method fn is not provided for an interface method, an UnsupportedOperationException will be thrown should it be called.”

http://clojure.org/java_interop#toc25