Thank you Kai for your post!!
>I think it is rather a Wicket/Spring integration question. Thus look at
>http://cwiki.apache.org/WICKET/spring.html
Yes, it's a very good link!!
>You have to
>
>1) Declare your wicket application in your application context, e.g.
><bean id="wicketApplication" class="project.MyApplication"/>
Yes, I did this in applicationContext.xml:
<!-- Setup the wicket Application -->
<bean id="wicketApplication" class="com.base.JPSApplication"/>
>2) Install a SpringComponentInjector in your application, e.g.
>class MyApplication extends WebApplication {
> public void init() {
> super.init();
> addComponentInstantiationListener(new
>SpringComponentInjector(this));
> }
>}
Yes, also did this:
public class JPSApplication extends SpringWebApplication implements
IUnauthorizedComponentInstantiationListener{
@SpringBean private LookupTableDAO ltDAO;
public void init(){
super.init();
addComponentInstantiationListener(new
SpringComponentInjector(this));
//for the SpringBean
InjectorHolder.getInjector().inject(this);
>3) Add the ContextLoaderListener to your web.xml
><listener>
><listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
></listener>
Also had this in my web.xml:
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
My error was that all my DAOs and my sqlMapClient was defined in a file
called persistance.ibatis.xml. I needed to include this file in my
applicationContext.xml :
<!-- IBatis Setup -->
<import resource="classpath:persistence.ibatis.xml"/>
Without this declaration it seems Spring couldn't find the DAOs.
Thank you once again for your assistance!!
Kind regards
Edwin
--
View this message in context:
http://www.nabble.com/Web-application-using-Wicket-and-iBATIS-can%27t-find-DAOs---...pls-help...its-urgent-tp21860375p21869434.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]