Author: kevin

The Committee involved in the development of the JDO2.0 spec (JSR243) voted no against the latest revised spec. Major concerns voiced by the parties involved (Intel, Iona, HP, JBoss, Oracle, SAP, Fujitsu, IBM, BEA, Notel) were consistent in that they are worried that the Java persistence approach will become fragmented if JDO2.0 is allowed to continue, and should concentrate on a migration path towards the upcoming EJB3.0 spec, which is gaining significantly more backing and approval than JDO.

Although Sun voted yes on the spec, their recently published letter to the community requests developers to pull together and adopt a common persistence approach, favoring the upcoming EJB3.0 spec. The letter describes JDO2.0 as being no more that a maintainence release for JDO, not a further development. This letter was quoted in a couple of the ‘no’ votes.

Parties who voted yes on the spec included Sun, Apple, Doug Lee and Apache Foundation.

The two leaders in the Java AOP space have announced they are merging their efforts and their projects to produce a combined AOP framework for Java.

AspectJ 5 will the the next version that will comprise of the two combined projects.

Dave Johnson (one of the Roller weblog developers has an interesting article about the development of a Weblogging client, BlogClient1.0, that interacts with most of the main popular blogging systems via a Web Services API.

Something I hadn’t considered, but I should check out sometime for my BBWeblog webapp (on which this blog is running).

I’ve posted a summary of the excellent book “Debugging the Development Process” by Steve Maguire, to my Book Summaries section.

This is an excellent book, recommended reading for any team/project lead, and also well worthwhile for any developer who wants to understand how they can work more effectively in a project environment (“Work smarter, not harder”).

I particularly like the main gist of this book, that so much time and effort is wasted on projects on “misguided effort”. A project/team can be made to be far more effective if the main goal is identified and held as the number 1 priority. I have seen this time and time again on projects – people get sidetracked off onto issues, either administrative or other non-essential development tasks, that do not contribute to the main goal in any way. An effective team/project lead needs to keep the teams focus, and shield the team from non-essential tasks.