What's Coming in Spring 3.0

This morning, I delivered my What's Coming in Spring 3.0 talk for the 2nd time at Colorado Software Summit. Since there is no Spring 3.0 source code to speak of, I was unable to do the "Choose Your Own Adventure" demo at the end. :(

The good news is I was able to easily upgrade the Spring Kickstart application from Spring 2.0 to Spring 2.5.5 (using annotations). When 3.0 is released, I hope to update this project to use 3.0 as well as show what I needed to change. If I get ambitious, I might even change the UI to use Flex or Ext JS to show a RESTful client. Below is my presentation - hope you enjoy.

Posted in Java at Oct 22 2008, 11:51:12 AM MDT 12 Comments
Comments:

Matt -

Nice presentation, was it recorded so that you will be able to put up the talk on the web?

Thanks for letting us know about the upcoming features in Spring 3.0. I hope that you are able to build a really sweet UI using Ext. If you need any help, feel free to contact me directly.

There have also been a few questions recently raised on the Ext forums about integration with AppFuse. If you could let us know about your experience with implementing an Ext front-end in the AppFuse environment that'd be great.

Thanks,
Aaron Conran
Ext JS Core Developer

Posted by Aaron Conran on October 22, 2008 at 07:00 PM MDT #

@Aaron - unfortunately, this talk wasn't recorded. If/when I create a Ext JS front-end for AppFuse, I'm sure you'll see me asking questions on the forums. ;-)

Posted by Matt Raible on October 22, 2008 at 08:31 PM MDT #

Spring really is loosing it. All the annotation junk, horrible. I love my application context, it is executable documentation. All the annotations transforms Spring from an IOC container to a Service lookup environment..

Posted by Peter Veentjer on October 23, 2008 at 02:08 AM MDT #

could you please suggest any resource where I can read more about Unified EL++? or better yet check it source code :)

Posted by Anton Malinovskiy on October 23, 2008 at 12:09 PM MDT #

Dubious. When I think expression language I think broken references and poor tool support.

Posted by Ivan Lazarte on October 23, 2008 at 01:21 PM MDT #

Don't spent too much time on a ExtJS User Interface. It is GPL and that scares a lot of enterprise-decision-makers. Having too securely refactor out every line of ExtJS code from Spring Kickstart just to be on the safe side would be a burden for using it.

I would like to raise a question on the architecture design. Why is it good to duplicate the exact same functionality across so many delegates?

Controller -> Manager -> Repository / DAO -> DAO

Isn't this absolute over-engineering? I agree that separating Controllers from Data access is a good thing, so that you can reuse data-access code inside complex services.

But the thought that creating so many layers for a simple "hibernateTemplate.find("from User")" should be a good thing is beyond me. Can somebody please explain?

Posted by Sakuraba on October 25, 2008 at 03:25 AM MDT #

To suggest that enterprise decision makers are "scared" to use Ext JS is FUD. Ext JS is dual licensed under the GPL+FLOSS and commercial. Any major organization not willing to jump on the OpenSource bandwagon is more than willing to fork over the cash for a closed source license. If you want free, go use dojo. You'll find after the time wasted with that turd, your team we be begging you to use Ext . Just my experience.

Posted by Mark P on October 26, 2008 at 11:03 PM MDT #

Matt, I see from the presentation that you're a beer connoisseur. Are you going to Devoxx (Antwerp)? I would by lying if I said Java was my primary reason for attending a conference in Belgium.

Posted by 6006604 on October 31, 2008 at 01:45 PM MDT #

Are you going to Devoxx (Antwerp)?

No, but I would like to go some year. I've heard great things about the conference and I'm certain the beer is delicious. ;-)

Posted by Matt Raible on October 31, 2008 at 08:46 PM MDT #

Sakuraba, Totally agree with you that the delegates is overengineering. Controller -> Manager -> Repository / DAO -> DAO This comes with a questions of many times we can reuse the Manager / DAO. For a small project, don't think the manager and dao will be resuse. For a big enterprise level project. Too many methods will be added different team into the manager and DAO. Eventually, these classes will be refractor into smaller classes that will be reuse a few times on on specific area only.

Posted by Chris lai on November 14, 2008 at 12:14 AM MST #

Hi
I'm pleased to announce the availability of a dedicated section to Spring 3.0 web resources at SpringHub.com. It is in the upper menu under Home > Tags > Tag: Spring 3.0.
Please click here for a direct access: Spring 3.0 web resources at SpringHub.com. Enjoy!

Posted by Slim Baltagi on March 16, 2009 at 08:56 PM MDT #

Good presentation, I have explained these features in detail through this article - http://www.myhomepageindia.com/index.php/2009/12/29/spring-mvc-3-0-tutorial.html

Posted by Deepak on February 16, 2010 at 04:03 PM MST #

Post a Comment:
  • HTML Syntax: Allowed