Comparing Java to Groovy NFJS talk online
The slides for my NFJS talk “Comparing Java and Groovy”, along with source code are now online in the Presentations section.
{ Category Archives }
Speaking
Groovy + Annotations + Aspects
I have been doing a lot of digging into Groovy and DSLs lately, getting ready for my OSCON talk next week.
The Groovy language has great built-in support for creating DSLs. Along with its dynamic nature, Groovy has the “use” keyword for working with categories, and coming in 1.1, the ExpandoMetaClass if you want to complete.
“Use”ing Categories
Categories help you do scoped “extension” to normal every day objects. An example is in order:
So, inside the use block, there is now (effectively) a new property on the Integer class, called tacos, that will return a string describing your delectable entree. This is a very powerful technique, and is very useful for developing your own expressive syntax.
One drawback to this technique is that you have to define where you are using it. Use can be extended into closures, but does not always extend into predefined methods.
-
-
}
-
-
-
// However, you can do this from Java (or Groovy):
-
-
-
// calling methods on a class:
-
class A {
-
4.tacos // has not been evaluated yet
-
}
-
}
-
-
-
// but you can do this:
-
}
Groovy + Annotations + Aspects = annotated “use” clause
I was talking about Groovy Categories with Blaine Buxton, and was telling him that I did not like having the “use” block inside my DSL code, and wanted a more transparent approach. He suggested that perhaps an Annotation and an Aspect would do what I was looking for.
With the 1.1-Beta1 Release, Groovy has built in support for Java Annotations, and since Groovy compiles down to byte code, there is implicit support for Aspects. Putting these two things together allows us to create an annotation for a more powerful use:
With a simple annotation, @Uses(category=[list of category classes]), we now can define them for any method we want, without having to put them into the method body.
Here is the Annotation code:
-
package com.nimblelogic.groovy.dsl;
-
-
import java.lang.annotation.Inherited;
-
import java.lang.annotation.Retention;
-
import java.lang.annotation.RetentionPolicy;
-
-
@Inherited
-
@Retention(RetentionPolicy.RUNTIME)
-
public @interface Uses {
-
public Class[] category();
-
}
And here is the Aspect code:
-
package com.nimblelogic.groovy.dsl;
-
-
import groovy.lang.Closure;
-
-
import java.util.ArrayList;
-
import java.util.List;
-
-
import org.aspectj.lang.JoinPoint;
-
import org.aspectj.lang.annotation.SuppressAjWarnings;
-
import org.aspectj.lang.reflect.MethodSignature;
-
import org.codehaus.groovy.runtime.GroovyCategorySupport;
-
-
public aspect UsesAspect {
-
-
pointcut allMethods(): call(@Uses * *(..));
-
-
@SuppressAjWarnings
-
List< class > classes = getCategories(thisJoinPoint);
-
-
Object result = null;
-
if ( classes.isEmpty() ) {
-
result = proceed();
-
} else {
-
result =
-
GroovyCategorySupport.use(classes,
-
new Closure(thisJoinPoint.getTarget()) {
-
@Override
-
return proceed();
-
}
-
});
-
}
-
-
return result;
-
}
-
-
@SuppressWarnings(“unchecked”)
-
private List< class > getCategories(JoinPoint thisJoinPoint) {
-
List< class > classes = new ArrayList< class >();
-
-
// get class level categories (if any)
-
Class cl = thisJoinPoint.getTarget().getClass();
-
-
addCategories((Uses) cl.getAnnotation(Uses.class), classes);
-
-
// get method level categories (if any)
-
if ( thisJoinPoint.getKind().equals(JoinPoint.METHOD_CALL)) {
-
MethodSignature sig = (MethodSignature) thisJoinPoint.getSignature();
-
addCategories((Uses) sig.getMethod().getAnnotation(Uses.class), classes);
-
}
-
-
return classes;
-
}
-
-
-
private void addCategories(Uses uses, List< class > classList) {
-
if ( uses != null ) {
-
Class[] classes = uses.category();
-
for(Class cl : classes)
-
classList.add(cl);
-
}
-
}
-
}
One thing to note when working with Annotations / Aspects in Groovy: you have to keep track of the build order. I struggled for a while to figure out why I was not seeing the annotation in my Groovy classes. It was because it had not been built yet! I ended up having to split my compilation into 4 parts:
- Build the Annotation
- Compile the Groovy code
- Compile my other Java code (just test code)
- Weave the Aspects
InfoTec 2007 Presentations are online
I put my InfoTec 2007 presentations online last night. If you don’t want to hear about how much fun I had giving them, here is the link.
My first talk was a 4 hour “Introduction to Ruby on Rails”. It had a decent turnout, and was a lot of fun to give. Thanks to a IM chat with Harish the night before the talk, I gave the best line I’ve given so far in a talk (IMHO): “So, what type of web application would you like to build today?”
My second talk was “Agile Java Web Frameworks”. There were twice as many people in this talk that had signed up before the conference started, though slightly fewer than in my rails talk. A slightly disjointed talk, I hit upon some of the more interesting web frameworks in the java world: Struts2, Spring MVC/WebFlow, Click, Rife, and then the dynamic contenders: Grails, Rails, and Lift.
Click was an interesting experience, as I had only learned about it the night before from Stephen Haberman. It looks pretty promising.
We only had enough time to quickly dive into one of the frameworks, and the audience chose Grails. So we delved into the bowels of GroovyQuiz and I showed them how it works.
Overall I had a lot of fun, and am looking forward to next years InfoTec.
Groovy DSL presentation now online
Last week I did a presentation for the Omaha Dynamic Language Users Group, entitled DSLs, Groovy, and YOU!. It was a lot of fun, and was well received. When you get down to it, everything we do as programmers is revolves around DSLs. There is definitely a blog post or three in that last sentence.
So, the files are online for the presentation, the handout, and for the Groovy partial-implementation of LOGO that I did for the talk.