Stephen Colebourne has a prototype implementation of the FCM closures proposal. I took some time to download and play with the new syntax and functionality.
I
tried to focus on some of the functionality FCM provides that other
closure proposals do not.
After three milestone releases Click 1.4 final is available for download. Major features include stateful page support, component event methods and a performance filter that helps you apply Yahoo Performance Rules.
How many times have you blamed your own laziness having found some highly meaningful check-in comment, like "fixed" or "done"? Even if you knew what it meant at the time of writing, after a while you will be unable to recall what has been done and why, and whether it reduces the backlog of your bugs or not ...
In a recent comment on my blog, Jared Peterson asked:
I'm curious if you have any thoughts on folks that might be trying to make a decision between Rails and Grails. I like the concept of "Allow Both", but what if you "have neither"?
If you were starting a new project, could choose either one, needed to interact with a lot of existing Java code (JRuby on Rails I guess), what would you pick?
This morning starts with good news. Having opened the press release on the Jolt Awards, I scroll through the page - here we are.
This post is an escape from XML redux. As stated in the last post, there are some who do not like to configure dependency injection (DI) in XML. They call it "XML Hell"!
In the last post we showed how using JSF to manage beans and perform some basic DI was very verbose. Then the post showed how simple DI with XML could be with Spring. Then we used Spring Java Spring Config to get rid of the XML configuration altogether.
This post uses Spring 2.5 annotation driven DI and scope management.
JPOX 1.2 was released March 2008. This is the first release after passing the JPA TCK.
JPOX passed JPA1 TCK in Febuary 2008 making it a JPA compliant persistence framework. This is the first full version that supports JPA 1, and JDO 1, JDO 2 and JDO 2.1.
JPOX like Hibernate provides transparent persistence for Java objects. Unlike Hibernate, JPA supports persistence to not only all popular RDBMS but also DB4O object datastore, and it supports JDO.
At the end of this month, I'll be moderating a Java Web Framework Smackdown at TSSJS in Vegas. I wasn't able to secure the boxing bell I used at a similar event at OSCON 2005, but I found one better on eBay today. See photo on right. ;-)
The following frameworks will be represented on this panel (+ possibly a few more if there's additional framework experts at the show):
As I mentioned in the previous post (which I accidentally published prematurely), I've been speaking on JavaFX Script at Sun Tech Days in Sydney, Australia. This was a great experience, as it was a well-run, informative conference. Of course, Sydney is a beautiful city, filled with wonderful people.
CMS Watch discusses Sun Microsystems CEO Jonathan Schwartz, speaking at the SugarCRM Customer and Developer Conference earlier this month, stating: "I think what you'll see from Sun," Schwartz remarked, "is that we're just going to take the 'J' off the 'JVM' and just make it a 'VM'." What does that mean? Here several of the DZone leaders share their views, from their various backgrounds, which range across a variety of programming interests and specializations.
OpenXava is a JPA Application Engine. You put your JPA classes and, in exchange, you will obtain a full featured application ready for production, and without code generation.