Delegating Scope
The next trick that Groovy builders perform is to delegate closure execution context back to the builder. This allows the builder to handle methods executed within the closure. This is important because it means all the nested method calls (that define nodes in the structure) are executed against the builder object rather than the current method scope, as would otherwise happen. Taking a closer look at the example:
b.screen {
title( "My Page" )
...
}
Normally, the title method would be invoked against the current method scope, but because the Groovy builders delegate the scope to the builder, the behind-the-scenes execution actually looks more like this:
b.screen {
b.title( "My Page" )
...
}
To illustrate this with an example, create the two classes shown in Listing 2.
The first class, NoDelegating, defines a screen method that takes a closure and then executes the closure and a title method. In the example tests below, the title method should never be called. The second class, SimpleDelegating, defines the same methods, but in the screen method it delegates the execution context of the closure to itself. The result is that any method calls made within the closure will be executed against the SimpleDelegating instance. The two tests below show the difference in behavior between the non-delegating and the delegating class:
@Test( expected = MissingMethodException )
public void noDelegationExample() {
NoDelegating b = new NoDelegating();
b.screen {
title( "My Title" )
}
}
@Test
public void simpleDelegatingExample() {
SimpleDelegating b = new SimpleDelegating()
b.screen {
title( "My Title" )
}
assertEquals( true, b.titleCalled )
}
Groovy Named Arguments
Another feature of the Groovy language that improves readability of builder code is the ability to define maps as a set of named arguments. Taking the navItem examples from above:
navItem( name: "Home", focus: true, visible: true )
navItem( name: "Admin", focus: false, visible: false )
navItem( name: "Logout", focus: false, visible: true )
The meaningless boolean arguments that were used in the first Java example are given context by using named arguments. You can see that the name of the first navItem is "Home" and it has focus and is visible. The construction of the other two items is just as easy to understand. When Groovy compiles down into Java code, this is equivalent to executing a method called navItem with a Map that has three entries with the keys of name, focus, and visible respectively.
New on the Java Boutique:
New Review:
Time Management Made Easy with the Quartz Enterprise Job Scheduler
Why not just use the Java timer API? This open source scheduling
API boasts simplicity, ease-of-integration, a well-rounded feature
set, and it's free!
New Applet:
Reverse Complement
Reverse Complement is a simple applet that converts DNA or RNA
sequences into three useful formats.
Elsewhere on internet.com:
WebDeveloper Java
Lots of Java information on webdeveloper.com
WDVL Java
Thorough Java resource at the Web Developer's Virtual Library.
ScriptSearch Java
Hundreds of free Java code files to download.
jGuru: Your View of the Java Universe
Customizable portal with online training, FAQs, regular news updates, and tutorials.
|