spring-webflow
spring-webflow copied to clipboard
Upgrade Web Flow to Spring 3 [SWF-1136]
Keith Donald opened SWF-1136 and commented
Includes:
- Spring 3 TypeConverter Integration
- Spring 3 EL Integration
- Spring 3 Formatter Integration
- Spring 3 Data Binding Integration
- Spring 3 UI Message Integration
- Spring 3 Validation Integration
- Spring Security 3 Integration After doing this work, there will be no more need for spring-binding.jar in Web Flow.
Affects: 2.0.7
Issue Links:
- #440 Spring 3 Type Conversion and Formatting Integration ("depends on")
- #441 Make Spring EL the default expression language implementation used in Web Flow ("depends on")
22 votes, 20 watchers
Tim Stavenger commented
I would presume that #354 Problem with integrating Spring MVC 3.0.0 M2 and Spring Web Flow 2.0.7 on a Portlet 2.0 container http://jira.springframework.org/browse/SWF-1136 is related to this issue? And perhaps #354 would be resolved when this issue is resolved?
Triqui Galletas commented
I would like to comment that one of the main things that keep me from upgrading from Spring 3.0.0M3 is that above that version spring forces you to use Tiles 2.1 or above (Don't know the exact versions) but Spring web flow has issues with Tiles Ajax View in versions of tiles above 2.0.7. I also think I had some problems with webflow, no ajax and tiles versions above 2.1.0. But I can't remember what it was, cause I already had enough of using all combinations of versions of spring, webflow, and tiles.
So, summarizing. Please make Spring 3 and WebFlow work with the same version of Tiles, so we don't need to go through the nightmare of experimenting which works with this combination of versions and what won't work with another combination.
For now I will stick to Spring 3.0.0M3, Webflow 2.0.8 and Tiles 2.0.7. So everything works except cascaded attributes.
Related: #324 and #312
Matt Benson commented
Will this also include support for Spring Security 3.x (http://forum.springsource.org/showpost.php?p=264465&postcount=7) ? Or should that go into a new issue?
Keith Donald commented
Yes, and we'll be addressing this in a 2.1 (evolutionary) and 3.0 (next generation) web flow series.
Rossen Stoyanchev commented
Removing 2.1 from the target versions as no further work will be done on it for Web Flow 2.1.