It’s been a while since I had time to blog. We’ve been busy. We raised $10m. As Adrian has pointed out, we’ve been very active in product development. I’ve written more code myself than usual in the last couple of months. (Mainly on experimental stuff, which may or may not see the light of day, but it’s fun, and sometimes I do something that turns out to be useful.) I’ve spent a lot of time speaking to press and analysts; we’re getting huge press interest these days. Press/analyst calls can be tiring, but can also be valuable, as many of these guys are smart and ask thought-provoking questions.
And the conference season has sucked up a lot of time. JavaOne was a big show for us, with all our sessions full and huge interest in Spring. For the first time, Interface21 was an exhibitor and we were all exhausted trying to speak to everyone who came to our booth. If you haven’t done it, you won’t appreciate how tiring wielding one of those badge scanners can be… Next week Mark Pollack and I are speaking about Spring.NET at Tech-Ed. This is my first Tech-Ed and is going to be an interesting contrast.
So much for Sun’s and Microsoft’s shows. The highlight of the summer conference season for the Spring team will be our European show, SpringOne, in Antwerp, Belgium, from June 20-22. This year, SpringOne has been extended to 3 days, and it will be a great opportunity to network with Spring developers, while you enjoy the best beer in the world. Registration is here.
All the recent and upcoming releases mean we’ll have plenty to talk about.
We’ve been talking a lot within the Spring team about best practices for configuration, and plan to write and speak about our conclusions. It’s worth drawing the big picture, as many people seem to miss it:
The Spring container has its own internal metadata, and it’s possible to contribute to that from different configuration sources. For example, we’ve long supported properties file overrides. The Pitchfork Project mixes in Java EE 5.0 annotations. There are many potential ways of defining Spring components. However you do it, you can use Spring out of the box services, extension hooks such as post processors, true AOP, Spring’s integration with countless third party products…
Thus by supporting additional configuration formats, we are not deprecating the XML syntax people usually use to configure Spring: just offering more choices that are consistent with Spring’s architecture.
At SpringOne, Costin Leau will be talking about ways to configure the Spring container, which should be an interesting session, and tackles this head on. One of the Spring Portfolio projects that Costin leads is Spring Java Configuration, which grew out of some of my experimentation a couple of years ago, and which I blogged about last November. That project configures Spring in Java: which of course can be mixed and matched with other forms of configuration.
SpringOne should be a good opportunity to interact with the Spring team and feed back your suggestions.
After Spring One, I’m looking forward to settling down in the same place for more than a couple of weeks. And I expect to have more time to write all the blog posts I’ve been thinking about for the last couple of months!