This article deals with the choices that Spring makes and the options that developers have for logging in applications built with Spring. This is timed to coincide with the imminent release of Spring 3.0 not because we have changed anything much (although we are being more careful with dependency metadata now), but so that you can make an informed decision about how to implement and configure logging in your application. First we look briefly at what the mandatory dependencies are in Spring, and then go on to discuss in more detail how to set your application up to use some examples of common logging libraries. As an example I’ll show the dependency configuration using Maven Central style artifact naming conventions.
The Spring Blog
A recent commentor here ragged, “It’s only half of the world that’s using Maven”, when pointing out it is not obvious how to obtain Spring 3 artifacts with Maven. In this entry, I’ll show you how to do this and what the options are. This information will also be integrated into the reference documentation of the upcoming Spring 3 final release.
Maven Repositories where Spring Artifacts are Published
In general, Spring publishes its artifacts to two different places:
We decided to publish a further Spring 3.0 release candidate before going GA: Get it from the download page, do a round of thorough testing, and let us know how it works for you. Spring 3.0 is now waiting for your integration test feedback and will eventually go GA in mid December.
This release candidate comes with several enhancements: e.g. extended functionality in the new <mvc:*> namespace, and a further revision of startup/shutdown behavior (affecting message listeners and scheduled tasks). Feel free to give those features an early try! We are also keen to learn about upgrade experiences with existing Spring 2.5 applications since we expect many of your applications to selectively adopt 3.0 features… while keeping the majority of the code in its 2.5 shape for the time being.
This week the Gemini project proposal was unveiled at Eclipse.org. Gemini is part of the Eclipse RT (runtime) project which is “designed to foster, promote and house runtime efforts in Eclipse, on the basis of the Equinox framework and OSGi” (Eclipse RT mission statement). Gemini itself is an umbrella project bringing together a collection of modules designed for enterprise application development. SpringSource and Oracle are the first two companies providing committers to the project, and several other companies have expressed interest in joining too.
We recently updated CloudFoundry.com. With this update, we introduced several exciting new features that pave the way for future development. I want to take this opportunity to describe and explain these features, as well as provide some background in how they came about. We are excited for you to try them out and provide us with feedback.
- Upload a tested application to Cloud Foundry
- Enable the maintenance page on the current deployment
- Clone the deployment
- Run a SQL script to migrate the database schema
- Redeploy with the newer version of the application
- Reconfigure the elastic IP so that the new deployment is served from the static IP address
- Stop the old deployment
The Spring 3 final release is right around the corner, and it’s going to be a great release. In this blog entry, I will take you through some of Spring 3’s type conversion and validation enhancements. Whether you are developing a traditional web application, a desktop application, or a “next-generation” RIA, data binding, type conversion, and validation are important areas. As you’ll see in this entry, Spring 3 gives you a significant upgrade in each of these areas while preserving backwards compatibility with previous releases.
We all love building applications with the latest and greatest technology however at the end of the day we are paid to deliver applications that achieve business goals. We spend each development iteration focusing on how best to achieve these goals but how do we know if the latest iteration achieved its goals? Did the latest release effect the existing business goals being delivered by the application?
SpringSource delivers this capability by giving you visibility into the application with Spring instrumentation, monitoring tools that show trends and reporting tools that allow you to export this data to the management team.
It is my pleasure to announce that we released the second Spring 3.0 release candidate today (download page). This release introduces key improvements over RC1 in several areas, in particular:
Spring 3.0 RC2 is fully JSR-330 compliant and passes the final version of the TCK. JSR-330, a.k.a. “Dependency Injection for Java”, basically standardizes an @Inject annotation with a qualifier model. The “javax.inject” annotations can now be used as alternative to Spring’s own @Autowired and @Qualifier annotations. Spring’s <context:annotation-config> element automatically activates JSR-330 processing as well (if the “javax.inject” API is present).
A dedicated AnnotationConfigApplicationContext: making programmatic bootstrapping as convenient as possible, without any XML involved. Explicit registration of annotated classes is supported as well as component scanning in the classpath. This works fine not only with Spring’s @Component model but also with @Configuration classes (a.k.a. “JavaConfig”) and JSR-330 compliant classes.
A new mvc configuration namespace: <mvc:annotation-driven/> activates rich processing of @Controller classes, including support for annotation-driven formatting and annotation-driven validation (if a JSR-303 “Bean Validation” provider such as Hibernate Validator 4.0 is present). The newly revised version of our formatting package also comes with support for the popular Joda Time library.
Revised lifecycle management at runtime: Auto-starting message listener containers and schedulers will now kick off once context configuration has been fully completed. On context close, a specific shutdown order can be defined for ‘phased’ stopping of lifecycle components. A configurable LifecycleProcessor delegate provides corresponding customization hooks.
Fresh from Arjen Poutsma's twitter feed: Spring 3.0.0.RC2 is now available. The release candidate contains lots of fixes to issues raised by community members and has also been updated to support the final versions of JSR-330 "javax.inject" and JSR-303 "javax.validation" APIs.