Comments on: Wicket/Spring/Hibernate configuration

By: Joonas

Joonas — Tue, 06 Apr 2010 12:09:15 +0000

@Erik: Do not use an interceptor. Simple as that; you’ll be much better off using event listeners. If you really have to use the interceptor (which quickly becomes a god-like class) then you can always implement ApplicationContextAware interface and manually fetch beans from that.

Btw, sounds a bit strange that your interceptor would have to have a sessionFactory reference. Perhaps its there by mistake?

By: Erik

Erik — Fri, 26 Mar 2010 13:02:21 +0000

I have been trying this for a while now but I can’t get it to work. I removed hibernate3-maven-plugin from the pom and copied the above code (with corrections). The sessionFactory and the interceptor have a cyclic dependency:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ’sessionFactory’ defined in class path resource [applicationContext.xml]: Cannot resolve reference to bean ‘interceptor’ while setting bean property ‘entityInterceptor’; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘interceptor’ defined in class path resource [applicationContext.xml]: Unsatisfied dependency expressed through bean property ’sessionFactory’: : Error creating bean with name ’sessionFactory’: FactoryBean which is currently in creation returned null from getObject; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name ’sessionFactory’: FactoryBean which is currently in creation returned null from getObject
I have searched a lot on the Spring forum and seen some advice on cyclic dependencies, like BeanPostProcessor, but I can’t get it to work. Does anyone here have the same experience and have solved the problem?

By: Alexandros Karypidis

Alexandros Karypidis — Wed, 10 Feb 2010 14:41:34 +0000

For those of you that want to work with Wicket 1.4.6:

There dependency on “wicket-spring-annot” is no longer required. Simply remove it. This package was used only in Wicket 1.3.

Its purpose was to add annotation support due to the fact that Wicket 1.3 could run on JDK 1.4, which did not have annotations. Starting with Wicket 1.4, JDK 5 (or later) is required and therefore the annotation support is not needed.

Remove the on that and it should work with Wicket 1.4 as well.

By: Simon

Simon — Sun, 18 Oct 2009 19:30:40 +0000

Great setup tutorial, tobad it doesn’t work! :-(

By: buddy

buddy — Tue, 18 Aug 2009 22:03:55 +0000

what is the name and path of the first file you created? it’s very difficult for a newbie to figure it out.

By: David

David — Tue, 04 Aug 2009 22:53:21 +0000

Hello Antoine, I am having similar problems. Did you ever get this to working?

By: Antoine

Antoine — Mon, 13 Jul 2009 21:47:39 +0000

Nice, haven’t got your example working yet using 1.4-rc6;

- for wicket-spring-annot version doesn’t work, seems like there are only versions for the 1.3 branch, so setting the version to 1.3.6 instead of ${wicket.version} should do the trick

- something seems to have gone wrong with the interceptor bean:

replacing the com.mycompany by org.springframework.orm.hibernate3 does not seem to be enough so guess something else went missing

finally, it is not mentioned the first file is applicationContext.xml

By: Michael Lange

Michael Lange — Fri, 05 Jun 2009 14:13:50 +0000

is the

applicationClassName
com.mycompany.WicketApplication

really necessary ? in my configuration it works without it

im still working with wicket 1.4, is http://cwiki.apache.org/WICKET/spring.html#Spring-AnnotationbasedApproach still the way to use spring beans inside page (and other) wicket classes ?

By: Stefan F

Stefan F — Fri, 05 Jun 2009 08:54:41 +0000

Cool stuff, bookmarked! This will certainly come in handy some day ;)

Could somebody make this to a maven archetype? That would be awesome!

Cheers, Stefan