Posted by Dean Wampler Tue, 26 Feb 2008 18:12:25 GMT
The new V0.4.0 release of Aquarium adds support for JRuby. Not only do the regular “pure Ruby” Aquarium specs run reliably under JRuby (V1.1RC2), but you can now write aspects for Java types with Aquarium!
There are some limitations and issues. For details, see my blog at Object Mentor and the JRuby page at the Aquarium website.
Posted by Dean Wampler Sat, 08 Dec 2007 18:02:14 GMT
I’m reprising my CJUG West talk on Aspect-Oriented Programming and Software Design in Java and AspectJ for the downtown Chicago group on December 18th.
I will briefly describe the problems that AOP addresses and how the principles of object-oriented design influence AOP and vice versa. If you’re in the area, I hope to see you there.
Posted by Dean Wampler Tue, 04 Sep 2007 22:55:00 GMT
I’m giving a talk at the Chicago Java User’s Group West meeting this Thursday at 6:30 PM. The topic is Aspect-Oriented Programming and Software Design in Java and AspectJ. I’ll briefly describe the problems that AOP addresses and how the principles of object-oriented design influence AOP and vice versa. If you’re in the area, I hope to see you there.
Posted by Dean Wampler Tue, 04 Sep 2007 15:51:00 GMT
I’m doing a tutorial on aspect-oriented design principles with examples in Java and AspectJ at OOPSLA this year. You can find a description here
Posted by Dean Wampler Sun, 25 Feb 2007 15:31:00 GMT
There was a recent post to the aspectj-users group from “Frustrated Newbie” who was trying to write adeclare error that would enforce the requirement that all classes implementing one interface, let’s call it Foo, also implement a second interface Bar. He tried something like the following:
declare error: within(*..Foo+) && !within(*..*Bar+):As an experiment (which he tried…), if you drop the second expression, leaving just within(*..Foo+) you get an error just on the Foo interface, not on any implementing classes or extending interfaces.
..foo and ..bar, respectively, the following does work:
declare error: within(*..foo.*+) && !within(*..foo.*) && !within(*..bar.*+): !within(*..foo.*) prevents errors on the interfaces in package foo itself.
This isn’t especially obvious and you may find it inconvenient to package your interfaces like this, but it does work. Actually, there’s a good case to be made for putting interfaces in separate packages like this, based on the Stable Abstractions Principle (PDF, see also here).
Posted by Dean Wampler Mon, 01 Jan 2007 00:38:00 GMT
I just released v0.7.0 of Contract4J5, which now supports Groovy and JRuby as alternative scripting languages, in addition to Jexl, the original language used. Along the way, I collected some performance numbers for the three alternatives.
The following discussion is adapted from the README for the v0.7.0 release.
I ran the JUnit test suite with all three languages. The numbers below show the performance when using binary weaving and load-time weaving (LTW) and also the performance using the JVMs in JDK 5 and JDK 6.
| JDK 5 (sec.) | JDK 6 (sec.) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Jexl | Goovy | JRuby | Jexl | Goovy | JRuby | ||||||
| Binary | LTW | Binary | LTW | Binary | LTW | Binary | LTW | Binary | LTW | Binary | LTW |
| 21.7 | 98.6 | 54.9 | 324.4 | 79.6 | 189.4 | 17.7 | 62.9 | 44.8 | 133.5 | 63.2 | 108.4 |
These times are approximate “user times”, averaged over a few runs, measured on a ThinkPad T42 running Ubuntu Linux. There are slightly different build activities and I/O overhead involved in the LTW numbers, adding a few percentage points to the numbers. The tests do some different manipulations depending on which interpreter is used. Hence, the results are rough, at best. Most likely, the numbers reflect the relative amounts of overhead to load the interpreters and to set up the “environments” for evaluating the scripts, which happens frequently in the test suite. Since the scripts are always very small, evaluation is probably not a large percentage of the execution time. (However, this is speculation!) Your mileage may vary…
Note that the JDK 6 performance is significantly better. The code was compiled
with the JDK 5 javac and executed using the JDK 6 JVM. Ironically, the performance was slightly slower when compiled with the JDK 6 javac. (This is not reflected in the numbers)
The Jexl test runs are roughly twice as fast as the Groovy and JRuby runs, probably because Jexl is a more “minimalist” environment, incurring less startup and execution overhead.
While not shown, I observed that the memory requirements for Groovy and JRuby are also higher, as you would expect. I didn’t actually measure memory usage, but I observed this because it was necessary to increase the maximum heap size for the LTW JUnit run when using Groovy or JRuby. Also, when using JRuby, I had to increase the heap size for the binary-weaving JUnit runs in Eclipse.
The LTW test runs take significantly longer, but the results are somewhat hard to interpret. Under JDK 5, the Jexl and Groovy runs are five to six times longer, while the JRuby runs are only about 2.5 times longer. Under JDK 6, the Jexl and Groovy runs are a little more than three times longer, while the JRuby run is under twice as long. It is not clear why JRuby LTW configurations perform so much better under both JDKs. However, it is clear that, for all the interpreters, the startup byte-code instrumentation required for LTW is much better under JDK 6.
In general, the longer LTW times occur because a weaving step happens at the beginning of each TestCase, as the class is loaded. The JDK 6 speed-up is a good argument for running this VM, at least for your tests!
LTW is the most convenient way to adopt Contract4J5 (true for other aspects, as well), but if the startup time is too long for your needs, then binary weaving of compiled code provides better performance with only a modest change in your build process.
Posted by Dean Wampler Mon, 01 Jan 2007 00:19:00 GMT
I just released v0.7.0 of Contract4J5. This release adds support for using Groovy or JRuby instead of Jexl as the scripting engine for the test scripts embedded in annotations. In fact, Groovy is now the default.
The advantage of Groovy or JRuby is that they provide a richer environment for more sophisticated testing. They are also better suited for planned, long-term enhancements of Contract4J5 to support user-configurable annotations and behaviors, which will take the tool beyond Design by Contract support.
The only major disadvantage over Jexl is lower performance. I’ll blog about those results next. You can also find details in the README.
I was pleased to find that all but a few of the existing Jexl-based unit tests worked without modification for Groovy. With a few hacks, I got them to work for JRuby as well. The differences for Groovy include slight differences in how Goovy vs. Jexl handle protected access (private, protected, etc.). Also, Groovy does not force you to provide a public accessor to evaluate tests on member fields, which Jexl required.
For JRuby, I found that almost all Ruby vs. Java differences could be handled if I did a few simple replacements of the most common Java idioms in scripts with the corresponding Ruby idioms:
equals(...) with eql?(...)compareTo(...) with <=>(...)null with nilThat is, Contract4J5, when using JRuby, will make these substitutions in your test expressions so they work, most of the time, even though they are written in Java syntax. This tends to work because the test expressions tend to be relatively simple and they often consist of comparisons to null or calls to String comparison methods.
Posted by Dean Wampler Fri, 22 Sep 2006 02:07:00 GMT
After a longer-than-expected effort, I’m pleased to announce the v0.6.0 release of Contract4J5.
The API for writing contract tests has not changed, but the internals have been restructured considerably to improve the code quality and make it easier to configure Contract4J5 using property files and Spring Framework Dependency Injection.
The release also provides examples of using Contract4J5 with binary weaving or load-time weaving. The latter is now the preferred way to introduce Contract4J5 into a “pure-Java” environment.
For more details, see the Release Notes in the README or browse to http://www.contract4j.org.
Posted by Dean Wampler Fri, 21 Apr 2006 16:25:00 GMT
I started a discussion yesterday on the “aspectj-users” group about humane pointcut languages. The notion of “humane interfaces” in programming has been discussed by Martin Fowler and in the context of user interfaces and product design by Jef Raskin.
This conversation was a spin-off of another thread where I made a mistake that I occasionally make. An AspectJ user wanted to apply some after advice after constructor calls in a class that has an annotation, e.g.,
@MyAnnotation
public class Foo {
public Foo(...) {...}
...
}
He needed help writing the pointcut and advice for this case. Without repeating the whole conversation here, at one point I remarked that
call( @MyAnnotation * *.new(..) )matches constructors annotated with
@MyAnnotation, while
call( * (@MyAnnotation *).new(..) )matches constructors in classes where the class has the annotation. In fact, both are invalid expressions because the first
* is for the return type and there is no return type for constructors, so the first * shouldn’t be there. Hence, the correct statement is that
call( @MyAnnotation *.new(..) )matches constructors annotated with
@MyAnnotation, while
call( (@MyAnnotation *).new(..) )matches constructors in classes where the class has the annotation.
This is the sort of mistake I make fairly often and I’m sure beginners really struggle with the pointcut syntax, although it’s generally great for experts because it is both succinct and powerful. However, sometimes a more “human-readable”, that is “humane”, syntax can be a real benefit.
In fact, I’ve been thinking about expressive pointcut languages quite a bit recently, not so much in this context, but more in the context of higher-level AOP abstractions. As I said in the discussion thread, it bothers me that we discuss high-level concerns, say for example security, then turn around and write PCDs using very low-level primitives that tend to reference specific classes, methods, etc.
Of course, I’m not the only person who thinks this way and the recent work on AO interface-based programming is a huge step towards making it possible to express aspects with appropriate levels of abstraction.
I would like to comment on this issue more in future blogs, but for now, let’s return to the original problem and look at some things we might do to make PCDs more humane.
The first thing I suggested in the thread is the addition of special keywords that could be substituted for some of the wild-cards:
| Keyword | Maps To: | Context |
|---|---|---|
$any_return |
* |
Used for any return type |
$any_arg |
* |
Used for any one method argument |
$any_arglist |
.. |
Used for zero-many method arguments |
$any_type |
* |
Used for any type expression (class, interface, ...) |
call( (@MyAnnotation $any_type).new($any_arglist) )
This is a little more readable, especially for new users, while experts will prefer the more terse form for its brevity.
As an aside, you could use a similar mechanism to support regular expression matching while minimizing the potential for confusion, as discussed here. Something like $re(/(foo|bar)$/) to match names ending in foo or bar, for example.
after advice, to see a little more context. We want to “bind” the newly-created Foo instance to a variable foo. Handling newly-created objects is tricky.
after() returning(Foo foo):
call( (@MyAnnotation $any_type).new($any_arglist) ) {
...
}
Another approach, if we’re using the execution join point, is the following:
after(Foo foo):
execution( (@MyAnnotation $any_type).new($any_arglist) ) && this(foo) {
...
}
However, the keywords are a small improvement. Let me suggest that a real “humane” PCD language should read more like English. Consider this rewriting of the same two expressions, using a made-up pointcut DSL:
after() returning(Foo foo):
call(constructors().takingAnyArgs().inClassesAnnotatedWith(@MyAnnotation)) {
...
}
and
after(Foo foo):
execution(constructors().takingAnyArgs().inClassesAnnotatedWith(@MyAnnotation))
&& bindNewlyConstructedObjectTo(foo) {
...
}
This syntax is inspired by the syntax of mocking frameworks like JMock and equivalents in Ruby. Certainly my toy DSL could be improved; I made it up on the fly during the discussion thread yesterday.
However, because it reads like English, it is very self-documenting, making comprehension easier by AspectJ neophytes and even experienced AspectJ users who are new to the application. I think it’s useful to remember that most code is write once, read many. We may not like to type a lot, but a literate style pays dividends over time.
Note that the syntax of this DSL and the standard syntax express essentially the same pointcut language “abstraction” for AspectJ.
So, I think there is a place for a more “humane” form of the AspectJ pointcut DSL. Similarly, I think that we need DSLs appropriate for higher-level AOP abstractions (e.g., at the design level) and ideally AOP DSLs that are domain-specific for non-trivial domains.
Read more...Posted by Dean Wampler Thu, 13 Apr 2006 18:34:00 GMT
This is my inaugural blog hosted on my own web sites. My previous blogs can be found here.
My article on Contract4J went live on Tuesday, April 11 at IBM’s developerWorks.
In the article, I introduce Design by Contract and describe how Contract4J supports DbC in Java, using AspectJ under the hood. I end the article with a discussion of the emerging trends in aspect-oriented design using interfaces. That is, how the familiar interface-based design we’re used to in OOP is being extended to support aspects.
I intend to explore Aspect-Oriented Design in more detail in coming blogs. Please stay tuned!
