No Hibernate Session bound to thread exception?

Spring version isn't your issue. I'd also recommend not annotating your DAO with transactions. Those belong on a service tier that has the DAO injected in.

That's where the session comes in as well: open the session for the use case, execute it, close the transaction, clean it up.

You forgot to enable annotation driven transaction management. In the link, search for tx:advice.

The tx namespace isn't recognized – Benchik Dec 30 '10 at 13:21 suucceeded to add but now I get an error: org.springframework.beans.factory. NoSuchBeanDefinitionException: No matching bean of type com.maxheapsize.dao. NameDao found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency.

Dependency annotations: {@org.springframework.beans.factory.annotation. Autowired(required=true)} – Benchik Dec 30 '10 at 13:31 Your bean implements an interface? You should autowire the interface and not the bean.It happens since your bean now was wrapped with proxy that implements the same interface, but it is not instance of a class.

– Tarlog Dec 30 '10 at 13:33.

One possible problem I can see here is that openSessionInViewFilter is mapped after UrlRewriteFilter . UrlRewriteFilter performs RequestDispatcher.forward() therefore all filters mapped after it should have dispatcher>FORWARD.

Only covers the local context in which it is defined. In this case, it will cover the beans in app-config. Xml, since that's the only place I see it in your configuration.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.