This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Check your logs... If you get a 404 yuor application didn't start properly, which indicates a configuration problem (in general). One thing I notice is you are adding hibernate4 as a dependency and using hibernate3 for your configuration classes, that obviously isn't going to work. Spring hasn't bean tested with 4.2 (AFAIK) I suggest sticking with 4.1.x for now (4.2 isn't final either it is still in development).

Also why do you have such weird classnames, not related but not common to use _ in classnames.

Final note your connection.* properties on hibernate are useless as you are injecting a datasource so those do nothing.

In addition to what Marten suggested it looks like you have your Hibernate JARs configured in your project as coming from a Library that is configured within your IDE (and not via Maven as the rest of your project). I wonder if the m2e (and m2e-wtp) integration is able to deal with this situation correctly and deploy those libs into your webapp when you deploy it to your tc Server.

You could check this by looking at the deployed app inside your tc Server instance folder. You should find your app there, along with all the libs that got deployed. And I guess hibernate is not there.

I think that would make sense, yes... But I think you don't need to add every single entry as a dependency, since Maven takes care of resolving transitive dependencies for you.

You could also take a look at the "Deployment Assembly" settings of your project (in the project properties). It shows you how the libs are deployed into the web app. Maybe the Hibernate library container from your classpath is missing there.