This post originated from an RSS feed registered with Java Buzz by dion. Original Post: Spring 2.x: Two pain points solved Feed Title: techno.blog(Dion) Feed URL: http://feeds.feedburner.com/dion Feed Description: blogging about life the universe and everything tech Latest Java Buzz Posts Latest Java Buzz Posts by dion Latest Posts From techno.blog(Dion)

It has been great to hear about the new Spring 2.0 features. There are a few much needed ones, but I was particulay interested to see solutions to pain points that I currently have:

Scoping

I discussed cleaning up scoping with JSF and Spring. The ugliness of having a jsf:scope attribute added via schema, and generated files is no more.

Spring 2.0 supports richer scopes, including web based ones (http session, request, etc) ThreadLocal, webflow conversations, and others. Being able to set the scope to these high level abstractions is needed.

Injecting Domain Objects

I run into, and need to use custom code for this one all the time. I want to inject a lot of the objects that I work with. One of the issues is that you want Spring to be in charge of the objects that you with to inject.

A common area in which this isn't the case is when you get objects from your persistence store (e.g. hibernate). Having to have routines takes these objects and inject them is a pain, as we want this code hidden.

This is where Spring 2.0 comes into play. It allows you, via AOP, to go into these domain objects and wire them up correctly.

Very, very, nice.