It has been quite a year for Spring.NET. We have gone through two milestone and two release candidates before the GA release in December. The first chunks of code for the 1.1 release were made way back in late 2004 by Aleks Seovic who started work on the ASP.NET framework. In short, it has been a long time in the making. Being the end of year, a natural time for reflection both past and present, I’d like to say thanks to the other members of the project and the Spring.NET community for all their contributions and support. I’m looking forward to a great 2008!
The Spring Blog
Mixing code in one and the same transaction that uses an Object-Relational Mapper with code that doesn’t, can cause issues with data not being available in the underlying database when it should be. Since this is a situation I come across once every now and then, I figured it would be helpful for all if I write down my solution to this problem.
In short: what I will present in the remainder of this post is an aspect that triggers the underlying persistence mechanism (JPA, Hibernate, TopLink) to send any dirty data to the database.
Sometimes important changes sneak up. Such changes aren’t driven by marketing campaigns, but by many individual decisions; there’s no fanfare; by the time they’re observed, they have surprising momentum. I mentioned one such development in my opening keynote at the recent Spring Experience conference: the steady rise of Tomcat.
Recently we’ve begun running polls on SpringFramework.org, and some of the results are interesting. The question Which application server(s) do you use? produced the following results: BEA WebLogic (various versions) and JBoss AS shared first place among Java EE app servers on 16% each, with IBM WebSphere just behind on 15% and Glassfish putting in a creditable performance on 5%. But the easy winner was Tomcat, on 37%.
In my recent post, I had mentioned that the Subversion repository for Spring Integration would be publicly accessible soon, and I’m pleased to provide that link now. You can checkout the project with the following command:
svn co https://anonsvn.springframework.org/svn/spring-integration/base/trunk spring-integration
If the checkout is successful, you should see the following directory structure:
spring-integration/ +--build-spring-integration/ +--spring-build/ +--spring-integration-core/ +--spring-integration-samples/
We are pleased to announce that the Spring .NET 1.1 final release is now available
- Inversion of Control Container
- Aspect-Oriented Programming Framework
- Aspect Library
- ASP.NET Framework
- ASP.NET AJAX Integration
- ADO.NET Framework
- Declarative Transaction Management
- Declarative Middleware Services
- NHibernate Integration
- NUnit Integration Testing
This release has been a long time in the making and the team would like to extend our heartfelt thanks to everyone who has contributed to the project.
Dear Spring Community,
we are pleased to announce that Spring IDE 2.0.2 has been released today. 2.0.2 is basically a bug fix and enhancement release, but finally adds tooling support for missing Spring 2.5 features like <context:* /> and <jms:* /> namespaces and the component scan facility.
The release is available from our release update site. Spring IDE 2.0.2 is compatible with current milestone builds of upcoming Eclipse 3.4 (aka Eclipse Ganymede).
Yesterday morning I presented a 2-part session at The Spring Experience entitled “Enterprise Integration Patterns with Spring”. The first presentation included an overview of core Spring support for enterprise integration - including JMS, remoting, JMX, scheduling, and email. That presentation also included a high-level discussion of several of the Enterprise Integration Patterns introduced in the book of the same name by Gregor Hohpe and Bobby Woolf. In the second presentation, I officially unveiled “Spring Integration” - a new addition to the Spring portfolio. Spring Integration builds upon Spring’s core support while providing a higher level of abstraction largely inspired by those patterns. Here I would like to provide a brief overview of the topics I discussed in that session. You can also read two articles about Spring Integration that appeared yesterday on eWeek and InfoWorld.
Dear Spring Community,
A summary of the more important changes:
- Added pooling library which features flexible connection validation and better configuration than the built-in pooling. Many thanks to Eric Dalquist for this contribution. (LDAP-85)
- Fixed a problem in AbstractContextSource which led to an unnecessary reference to the LDAP Booster Pack (ldapbp). (LDAP-88, LDAP-89)
- Fixed bug in SimpleLdapTemplate where the wrong target method was being called. (LDAP-93)
- Made createContext in AbstractContextSource protected rather than package private. (LDAP-94)
Dear Spring community,
I'm pleased to announce that Spring Web Services 1.5.0 M1 has been released.
This milestone release introduces:
- JMS transport support, for both client- and server-side
- Email transport support, also for both client and server
- Two new Spring namespaces, which drastically decrease the amount of XML to configure marshallers and typical Spring-WS constructs
- SOAP 1.2 Compatible WSDL descriptor generation
- Spring-WS jars are now OSGi bundles
I was cruising the blogosphere today and encountered one of the shortest blogs I’ve ever read. To quote nearly the entire entry, “Every time you use Acegi, a fairy dies. The sad thing is there really isn’t anything better around…”.
Between our community forums, developer lists, JIRA, user conference BOFs, training, support, consulting and team blog, we receive a great deal of community feedback. There is little doubt that many people have sought improvements to the Spring Security (formerly Acegi) configuration format, and we’ve invested a lot of time in making that possible.