Dear Spring community,
I'm pleased to announce that Spring 1.2.9 has finally been released. Download | Docs | Changelog.
This is a bugfix and refinement release for people still using the 1.2 series, and is intended as a drop-in update for Spring 1.2.8. It contains fixes for all problems reported since 1.2.8, and includes various backports from the Spring 2.0 branch.
Note that this is the last planned release in the Spring 1.2 branch. Patch releases for 1.2.9 will only be provided in case of critical issues. We recommend to upgrade to Spring 2.0 for long-term usage.
The Spring Blog
Dear Spring community,
At long last I can finally say that SPR-1484 is resolved. Opened on 20 November 2005 with 121 votes, 63 watchers, and even its own anti-ticket this issue rates as one of the all time biggies. In the last 10 minutes I’ve uploaded the maven artifacts for Spring 1.2.9 to our local repo and you should be seeing them replicated onto the central maven repo in the next 6 hours or so.
You will notice on the Spring JIRA issues such as SPR-2704, SPR-1383, and SPR-3198. What this means is that we’re not done improving our builds and and we will continue to respond to the community. In fact, we’ve got some really cool new tools that I can’t wait to show off in upcoming posts.
On the theme of application servers embracing Spring, another update. Oracle have been working on value added integration with their application server.
This is similar to what we have with WebLogic 8.1 and above in WebLogicJtaTransactionManager. The OC4JJtaTransactionManager should be used in place of the generic JtaTransactionManager in an OC4J environment, and provides the following benefits:
- Direct access to the transaction manager and helper classes without having to use
- Auto-detection of server version to get the most out of the different transaction manager implementations in different versions
- Control over transaction isolation level: a very useful feature not available in JTA
Sun take open source seriously these days, and users seem to be starting to take Sun open source seriously too.
GlassFish was late to the party in open source application servers, but it seems to be gaining traction. And, more importantly, it actually seems to be pretty good. Various Interface21ers, including Costin and Juergen, have taken a look at GlassFish and given it the thumbs up (although we haven’t yet worked with it in production). From what I’ve heard, performance is excellent–probably substantially due to the reworked servlet engine based on NIO. The JPA implementation–TopLink Essentials–should perform well too, being based on the mature and performant TopLink engine.
Congratulations to the WebLogic team on shipping a preview of WebLogic 10, which passes the Java EE 5 CTS. It’s good to see BEA getting back to their tradition of being quick off the mark, after their aberration with J2EE 1.4.
This is interesting news for the Spring community, because WebLogic 10 uses Pitchfork internally. The Pitchfork Project is an open source project led by Interface21 and collaboratively developed with BEA that implements EJB 3.0 interception and JSR-250 injection on top of Spring. It is used inside the WebLogic 10 EJB container and in other parts of the server to meet new spec requirements, but is not tied to WebLogic. Pitchfork can be used standalone (although that’s not its primary goal) or could be adopted by other application servers.
Between Rod’s recent blog on the origins of the Interface name, a recent thread querying the renaming of Acegi Security, and a suggestion late last year from my colleague Ben Hale to blog about the origins of the “Acegi” name, I’ve decided that it’s probably time to do so!
First of all, the pronunciation: it’s “ah-see-gee”. Now that we’ve got that out of the way, let’s go through where it came from:
- Back in the early 1990s, I started a bulletin board system. I still remember using my first 300 baud modem, and actually watching the characters appearing at the same speed as I could read them! Anyway, a BBS required a name, and I quite liked “Midnight BBS” (or was it “Lightning BBS”?). After attempting to register my preferred name with the Australian BBS Registry, I received a phone call to be informed that the name was taken. I searched for another name, found no conflicts, and changed all of my screens (anyone remember Avatar?). I then went to register the BBS with its new name, although someone else had just beaten me to the same name. There were about 800 BBSes in Australia around the time - this was competitive stuff! So, I decided to go with something that was guaranteed to be original: characters 1, 3, 5, 7 and 9 from the English alphabet. Acegi BBS was then born.
- This was the BBS heyday. It had callers from all across Australia, and it was the first BBS in our area code to acquire the seemingly limitless capacity of a CD-ROM. I became the 3:624 network coordinator for Fidonet and helped distributed “echomail” throughout our region. Before long, people started sending cheques payable to “Acegi BBS”, as they wanted greater file download limits and access to Fidonet’s netmail.
- Because I needed to cash cheques with “Acegi” in the name, in early 1993 we decided to register a business name. Acegi Computer Technology was selected, and people happily made out their cheques accordingly.
- In about 1995, I moved to Sydney with work. Dial-up Internet was just starting to become publicly available in Australia (it still cost around $5 per hour for modem access!). Because a BBS draws most of its users from a particular local area and I was leaving that area, I gave Acegi BBS to a friend to continue running. He too subsequently moved, and passed the BBS to another friend. I lost track after that. I did a Google for “Acegi BBS” and even found an old 1995 record of it.
- By 1996 I needed a company for my IT projects, so Acegi Technology Pty Limited was born. It has remained operational since.
- Sometime around November 2003, I wrote what eventually became Acegi Security. I put it into a ZIP file and shot it across to Rod and Juergen. I proposed the new project be called “Spring Security”. However, they didn’t have time to fully review it at that stage, so suggested I simply get it out there as “_____ Security System for Spring”. As such, I prefixed “Acegi” into the name. As of today there are about 660,000 hits on Google for a search of “Acegi”, and nearly all of it relates to the security framework.
Spring 2.0.1 introduced an
AbstractRoutingDataSource. I believe that it deserves attention, since (based on frequent questions from clients) I have a hunch that there are quite a few ‘home-grown’ solutions to this problem floating around. That combined with the fact that it is trivial to implement yet easy to overlook, and now I have several reasons to dust off my corner of the team blog.
The general idea is that a routing
DataSource acts as an intermediary - while the ‘real’ DataSource can be determined dynamically at runtime based upon a lookup key. One potential use-case is for ensuring transaction-specific isolation levels which are not supported by standard JTA. For that, Spring provides an implementation:
IsolationLevelDataSourceRouter. Consult its JavaDoc for a detailed description including configuration examples.
I had a great time at the Spring Experience conference last month. One pleasant surprise I had was the extent of the recent work the Spring IDE team have been doing. I ran into Spring IDE developer Christian Dupuis several times at the conference, and it seems that each time he’d implemented a new feature…
The forthcoming 2.0 release of Spring IDE is a comprehensive update to match the new features in Spring 2.0. And the Spring IDE team is making great progress with two of the big ticket items: XML extension namespaces and the AOP enhancements. (Btw, in case you’re wondering why I haven’t posted for a while, I spent a lot of time writing a Spring 2.0 update article over at InfoQ. This goes pretty deep with XML, AOP and core container features.)
Recently I've been doing some work with a client on WAS 6.1. Since we have a number of Spring users on WAS and I need to test the application, I decided it was time to get a copy of WAS running on one of my work laptops. I say 'one of' because I'm currently working on both my Mac (with OSX) and my ThinkPad (with Ubuntu) - more recently I've just been using the ThinkPad because I can have Oracle XE and WAS running without the need for a VM tool like Parallels. I still prefer the Mac, but to be honest there isn't much difference day-to-day - I just miss some of the more useful Mac tools like Spotlight, Quicksilver, TextMate and NewsFire.