To learn more about the Micro Cloud Foundry, check out these three blog posts introducing Micro Cloud Foundry to Spring developers and Grails developers, and introducing the support for Micro CloudFoundry in SpringSource Tool Suite. In this latest post, he cautions that while using the conventions in some cases can be very helpful (such as with ), using some defaults can cause confusion. This is a fair point, and it's nice to have the choice, either way. Nice work, Roger! This blog post highlights the fact that Spring.NET supports bi-direction injection, a feature…

That said, this post is a very good read. TomcatExpert.com comments on the support for explicit release of JNDI resources in Apache Tomcat. Apache Tomcat 7 contains a number of new features around database connection pooling, which help administrators keep their application available and serving content, collecting customer information, and supporting their applications. The main one that has garnered a lot of attention is the new JDBC Connection Pool feature introduced by Filip Hanik last year. Another connection pool attribute not yet discussed here on TomcatExpert.com is the new…

Today VMware team released Micro Cloud Foundry, a complete, local version of the popular, open source Platform as a Service that lets developers run a full featured cloud on their Mac or PC. Using Micro Cloud Foundry developers can build end-to-end cloud applications locally, without the hassles of configuring middleware while preserving the choice of where to deploy and the ability to scale their applications without changing a line of code. Micro Cloud Foundry supports Spring and Java, of course, but also provides runtime environments for Scala, Node.js, and Ruby so that you can release your…

Spring has rich support for transaction management through its PlatformTransactionManager interface and the hierarchy of implementations. Spring's transaction support provides a consistent interface for the transactional semantics of numerous APIs. Broadly, transactions can be split into two categories: local transactions and global transactions. Local transactions are those that affect only one transaction resource. Most often, these resources have their own transactional APIs, even if the notion of a transaction is not explicitly surfaced. Often it's surfaced as the concept of a session, a…

and a FactoryBean whose definition is thus:

This post explain's one architect's reasoning. Are you fleeing from CDI and JavaEE6, and moving your application to Spring? Or, simply want to reuse code from an existing CDI application, in particular CDI's decorators? Then check out this post for an approach to reuse CDI's decorator's inside of Spring. This support is limited in scope, of course, but it's one less thing you'd have to work on when moving to Spring. An ideal migration will take advantage of the far more robust AOP support available in Spring itself.

It's been a long road, but it's great to see this powerful framework reach 1.0 GA. Check it out! Users of Tapestry's templates as well as JSF's Facelets will see a lot to like in this view template technology - check it out!

Dear Spring Community, I am pleased to announce the release Spring Integration, 2.0.5. This release addresses 48 issues of which roughly half were bugs and half were improvements. For details see: Downloads | JavaDocs | Reference Documentation | Changelog