I just got finished with my Spring 2.0: New and Noteworthy talk at Atlanta DevCon 2006. Let me be the first to say that the conference was great. The site and organizers were all top notch. I'd like to give a special shout-out to Burr Sutter for putting on one heck of a conference. You know that things are going well when the conference center doesn't have a wireless network but you can get the one from the cafe next door. That's good karma! The JUG members were all very knowledgeable (even the ones that didn't know about Spring) and asked great questions. I fielded questions about EJB…

Dear Spring community,

We are pleased to announce that Spring 1.2.8 has been released. Download | Docs | Changelog

This is a maintenance release, fixing a number of issues found in previous 1.2.x releases. Most of these fixes have been backported from 2.0 M4, so have already been available there. Please see the changelog for details.

Juergen
-----
Juergen Hoeller
Lead, Spring Framework Development
Chief Architect, Interface21
http://www.springframework.org
http://www.interface21.com

Dear Spring Community,

We are very pleased to announce that Spring Web Flow (SWF) 1.0 RC1 (Release Candidate 1) has been released.  Download it.

After over a year of hard development work, 29,000 downloads, 3,700 posts by 500 forum users, one book, and numerous community-driven articles, this release delivers the first 1.0 release candidate of Spring Web Flow.  Considered fit for production use, this release solidifies the 1.0 API which will remain backward compatible throughout the entire 1.x series.

To the Spring Web Flow early adopters and champions who have supported our product, thank you.  Spring Web Flow delivers one of the most innovative and powerful controller engines available today thanks to your feedback and support.

The Spring Web Flow team expects one more release candidate before 1.0 final.  The new and noteworthy in 1.0 RC1 include...

NEW AND NOTEWORTHY

This support is illustrated by the simple NumberGuess sample application, where a "Game" component managed by the flow carries out the execution of game business logic.  The component itself has zero dependencies on Spring Web Flow APIs.

 To demonstrate, the business interface of the Game component could be defined as:

The flow definition to carry out execution of a Game with a user could look like: 

Lastly, the binding between the logical game action identifier and a Game implementation is made by Spring within game-beans.xml.

The HigherLowerGame implementation is also completely decoupled from Spring and Spring Web Flow APIs. 

Enhanced support for flow variables, created automatically when a flow starts.  Flow variable values may even be sourced from a backing bean factory, benefiting from full dependeny injection there.  The exact scope of the variable is configurable.

A new flow execution redirect response type, for redirecting to a unique "flow execution URL".  Accessing a flow execution URL refreshes a  Flow at a previously entered ViewState, allowing continuation from there.  The URL remains valid while the conversation is active and the continuation point remains valid.  This allows for full use of back, next, refresh, and new window buttons without page caching.

Refinements in state exception handling, with convenient support for transition-executing state exception handlers.  The core transition element now supports a on-exception attribute that drives a transition to a new state on the occurrence of an exception.  For example:

... transitions the flow to the editAccount state if an AccountException is thrown by the placeOrder method.

Improvements in flow attribute mapping support.  Each flow may now be configured with an input-mapper to map input provided by callers that start the flow.  A flow may also be configured with an output-mapper to expose return values to callers who terminate the flow.  These enhancements allow a flow to be reused as a top-level flow and a subflow without change, as input and output attributes are mapped consistently for both cases.

Support for dynamic view name and target state expressions, allowing for convenient runtime-based calculation of ViewState's logical view name, and a transition's target state, respectively.

Enhanced JSF integration.  The JSF integration now supports the logical redirect response types including FlowExecutionRedirect, ConversationRedirect, FlowRedirect, and ExternalRedirect.  In addition, enhancements to the FlowPhaseListener allow for a flow execution to be launched and refreshed without having to go through a formal navigation step.  1.0 RC2 is expected to add further JSF convenience and official support with JSF in a Portlet environment.

ADDITIONAL RESOURCES and WHERE TO START

Spring Web Flow 1.0 RC1 further refines the reference manual, providing 50 focused pages on SWF usage.  The manual is available on-line in HTML and PDF forms.

One of the best ways to get started with Spring Web Flow is to review and walkthrough the sample applications.  We recommend reviewing all samples, supplementing with reference manual material as needed from the start.  Nine (9) sample applications ship with the 1.0 RC1 release, each demonstrating a distinct set of product features.  These samples are:

1. Phonebook - the original sample demonstrating most features (including subflows).
2. Sellitem - demonstrates a wizard with conditional transitions, flow execution redirects, conversational scope, and continuations.
3. Flowlauncher - demonstrates all the possible ways to launch and resume flows.
4. Itemlist - demonstrates REST-style URLs, conversational redirects to a refreshable conversation URL, and inline flows.
5. Shippingrate - demonstrates Spring Web Flow together with Ajax technology (thanks to Steven Devijver)
5. NumberGuess - demonstrates stateful beans
6. Birthdate - demonstrates Struts integration.
7. Fileupload - demonstrates multipart file upload.
8. Phonebook-Portlet - the phonebook sample in a Portlet environment (notice how the flow definitions do not change)
9. Sellitem-JSF - the sellitem sample in a JSF environment (notice how the flow definition does not change)

To build the sample applications for deployment in one step simply extract the release archive, access the projects/build-spring-webflow directory and execute the ant dist target.  See the release readme.txt and projects/spring-webflow-samples/readme.txt for more information on the release archive contents and samples, respectively.  All sample projects are now Spring IDE projects, directly importable into Eclipse.  Watch for the Spring IDE Graphical Web Flow editor coming soon from the Spring IDE team.

Thanks to everyone out there who has made Spring Web Flow what it is today—those using it, providing the feedback that makes it stronger.  Enjoy!

Sincerely,

The Spring Web Flow Team

Keith Donald
Erwin Vervaet
Colin Sampaleanu
Juergen Hoeller
Rob Harrop

In a project that I used to work on we had a system that would receive messages from a device and make decisions on whether that information would be passed to the user. There were multiple decision levels and one of the problems we always found ourselves asking was if a message was being lost on it's way through the system.

Before we moved to Spring, it was nearly impossible to tell the answer to that question. Attempts were made to use logging, but the sheer volume of messages that decisions were made on made it tedious at best. Other attempts were made using debuggers but a combination…

Dear Spring Community,

We are pleased to announce that Spring IDE 1.3 has been released.

This release of Spring IDE provides some new features and a bunch of bugfixes. For a complete list visit http://springide.org/project/milestone/Release%201.3

Changes:

• Now Eclipse 3.1 and Web Tools are required!!!
• Updated to Spring 1.2.7
• Updated version of BeansXmlEditor
• Support for searching the BeansCoreModel
• Open Spring Bean dialog (similar to JDT's "Open Type" dialog)
• Wizard for creating a new SpringProject
• BeansView can be linked to BeansXmlEditor
• Now any filename extensions for BeansConfig files are supported

More details are available from the project's site http://springide.org/

Use Eclipse's update manager to install this this release from the project's update site http://springide.org/updatesite/

For bug reports tickets can be opened via http://springide.org/project/newticket

Dear Spring community,

We are pleased to announce that Spring 2.0 M4 has been released.  Download | Docs | Changelog

Spring 2.0 M4 is the fourth milestone of the next generation of Spring.

The new and noteworthy include:

• updated JPA support
• named parameter support for JDBC acces
• refined XML schema namespaces
• auto-proxying for FactoryBean-created objects
• and many other refinements noted in the changelog.

This release also contains numerous fixes for issues discovered since M3.  Users of previous milestones are encouraged to update.  See the changelog for details on all M4 changes.

With this release we are approaching a feature freeze for the 2.0 production target, with only a few further features and refinements planned for inclusion in 2.0. The next release will be Spring 2.0 Release Candidate 1 (RC1), scheduled for May.

We will also release a 1.2.8 maintenance release within a few days, backporting all applicable fixes from 2.0 M4. (This is already available from mbranch-1-2 in CVS, awaiting final tests.)

Enjoy and keep the feedback rolling in,

Juergen
-----
Juergen Hoeller
Lead, Spring Framework Development
Chief Architect, Interface21
http://www.springframework.org
http://www.interface21.com

Recently I was working on a project that had a Swing client communicating via RMI to a service layer. The service layer was marked with transactions and everything seemed to work fine. However everytime we'd get an exception at the Hibernate DAO layer, Spring would turn the exception into a runtime exception and it would get propagated all the way up the stack and across the RMI connection as a RemoteException. Whenever the exception was deserialized there would be an exception on the client (separate from the RemoteException.The decision was taken to simply introduce an aspect. Any exception…

With the release of Spring 1.1 the Spring community was given it’s first taste of JMS support. This support included exception translation, message conversion, and a template class much like JdbcTemplate. This support also took care of domain unification between the JMS 1.0.2 and 1.1 specs. The centerpieces of this support are the JmsTemplate class and it’s JMS 1.0.2 counterpart JmsTemplate102.

This support was a great improvement over using the raw JMS APIs to do enterprise messaging. However it did have a shortcoming; the JmsTemplate only supported synchronous reception of messages using the JmsTemplate.receive() methods. This behavior worked well for many people but the vast majority of users of ended up rolling their own implementations of an asynchronous consumer. In short, they wanted what EJB 2 called Message Driven Beans…

While the material in this post is quite simple, it will actually offer a glimpse of some rather significant new features in Spring 2.0. I hope that with a little imagination, you will be able to apply what you see here to far less trivial use cases of your own.

I am going to show 2 examples actually. The first will use a rather simple logger:

package example;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

public class SimpleLogger {

  private static Log log = LogFactory.getLog(SimpleLogger.class);

  public void logOneString(String s) {
    log.info…