Tag Archive for '2.1'

2.1 with Web Flow 2 support released

Just in time for the 2.0.3 release of Spring Web Flow we are proud to announce the availability of Spring IDE 2.1 bringing support for Web Flow 2 and Eclipse 3.4.

After the Ganymede release some users had problems installing Spring IDE 2.0.6 into their shiny new 3.4 packages. This was basically due to incompatibilities between Spring IDE’s Mylyn integration and the Mylyn 3.0 APIs which changed quite significantly. Thanks to a rapid pair programming session with Mik Kersten, lead of the Mylyn project at Eclipse, we were able to make Mylyn 3.0 support available just hours after the Ganymede launch from the Spring IDE nighty update site (It is so much fun sharing an office with the Tasktop crew. If you are ever in Vancouver make sure to drop by for a coffee). Obviously an nightly snapshot build is not everybody’s preferred installation source; therefore I’m more than happy to announce that version 2.1 is now officially compatible with Eclipse 3.4 and Mylyn 3.0.

Besides the usual bug fixing that goes into every release and the fore-mentioned Mylyn and Eclipse migration, 2.1 now supports Spring Web Flow 2. We have added support for visual editing using the graphical Web Flow Editor as well as support for validating and editing of the XML flow definition files based on the 2.0 XML schema. It is important to note that 2.1 does not break the Web Flow 1.x support. So all Web Flow 1.x users out there: it is safe to upgrade to Spring IDE 2.1.

Another feature, rather small but requested quite often, is the ability to display nested beans in the Beans Dependency Graph. See the following screenshot for an example.

Beans Graph with inner beans

As always the release is available from the update site hosted at Amazon S3. Here are the links:

In closing I would like to mention that Spring IDE 2.1 serves as the foundation for the upcoming SpringSource Tool Suite 1.1 and SpringSource Application Platform Tools 1.0 release (later next week). Over the last months we have added extension points and APIs to Spring IDE that provide some nice and supported ways of extending the Spring structure model provided by Spring IDE.

Spring Web Flow 2 Support on the Way

For those of you who want to use Spring IDE with Spring Web Flow 2 I have good news today: The support for Web Flow 2 is now available as part of the Spring IDE 2.1 development snapshots from the nightly update site at http://springide.org/updatesite-nightly. If you are Web Flow user please give this a try and report in JIRA if something is not working as it should.

The nightly build also contains a Mylyn Integration feature that is compatible with Eclipse Ganymede and the Mylyn 3.0 release.

Update: fixed the link to the update site. Please note that the link is intended to be used with the Eclipse update manager and not with your browser as Amazon S3 is not very browser friendly.

Last Minute Features for 2.0

Due to a bug in one of Spring IDE’s validation rule that was fixed post-RC1 and a small glitch in Spring’s AOP namespace handler implementation, our latest nightly build ships a Spring 2.1 OSGi bundle. Therefore we could enable the support for two additional features that were already implemented.

The AOP feature now supports Spring 2.1’s new bean(<name pattern>) pointcut primitive that enables you to specifiy a certain bean or a set of beans for pointcut matching. For example the pointcut definition

<aop:pointcut expression="bean(serviceBean)" />

would only match on a bean named serviceBean. Certainly you can combine the bean pointcut primitive with any other primitive that is supported by Spring. It even works for @AspectJ-style aspects.

The second and last new feature - we are now feature complete for the 2.0 stream - is support for <context:component-scan />. Read Mark’s blog for more information on this new feature. Beans created by the class path scanning infrastructure are recognized by Spring IDE and handled as normal beans; though they are visually marked with an @ icon decoration.

Spring Quick Fixes

With having implemented pretty much every open UI-related ticket with the upcoming 2.0 RC1, we are now planning the post-2.0 roadmap and therefore I just want to raise your awareness to an open enhancement ticket in our ticketing system that requests support for Quick Fixes on Spring IDE error markers.

I would really want to get some more input on what kind of Quick Fix you guys find useful and want to see in Spring IDE 2.1. So please head over to the ticket and add your comment to it.

Talking about UI features: Have you noticed that we have added a custom Spring working set type that can help reduce the clutter in Spring Explorer? Just use the normal Eclipse dialogs to configure a new working set of type Spring.