Setting up Spring + Wicket on Websphere 5

Posted by: Joshua on: November 14, 2007

In: Java
Comment!

Generally you won’t find any problem setting up Wicket on Websphere 5 using WicketFilter. But there are some situation where you just can’t use WicketFilter. One case of that is if you integrate Wicket with Spring, then you’re in trouble. Why?

ContextLoaderListener doesnt’ work on Websphere 5 which is another darkside of Websphere because Servlet 2.3 spec already support listener and it should work on any container.
That means you need to use ContextLoaderServlet.

Is that it?
No. You’re still on another problem.Filter is loaded first before servlet. So you would end up in an exception saying that Wicket can not find your spring context. Thank’s God Wicket also provides a WicketServlet (though this has been deprecated and not recommended to use anymore) for situation like this. And you would not lose all the functionality in WicketFilter because basically WicketServlet will instantiate WicketFilter and call it once it is loaded.

To wrap it up, this is the web.xml configuration you would likely use for such situation:


<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
	"http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>
	<display-name>wicket</display-name>

	<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/applicationContext*.xml</param-value>
	</context-param>

	<servlet>
		<servlet-name>context</servlet-name>
		<servlet-class>org.springframework.web.context.ContextLoaderServlet</servlet-class>
		<load-on-startup>0</load-on-startup>
	</servlet>

	<servlet>
		<servlet-name>wicket.wicket</servlet-name>
		<servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet-class>
		<init-param>
<param-name>configuration</param-name>
<param-value>development</param-value>
		</init-param>

		<init-param>
<param-name>applicationClassName</param-name>
<param-value>com.taxandtech.lab.wicket.web.WicketApplication</param-value>
		</init-param>

		<init-param>
<param-name>applicationFactoryClassName</param-name>
<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
		</init-param>
		<load-on-startup>1</load-on-startup>
	</servlet>

	<servlet-mapping>
		<servlet-name>wicket.wicket</servlet-name>
		<url-pattern>/app/*</url-pattern>
	</servlet-mapping>
</web-app>

Then you call your Spring beans from WicketApplication class as such:

public class WicketApplication extends WebApplication
{
    private DepartmentService departmentService;

    public DepartmentService getDepartmentService() {
        return departmentService;
    }

    public void setDepartmentService(DepartmentService departmentService) {
        this.departmentService = departmentService;
    }

}

And this is an example how your applicationContext configuration would look like:


<beans>
    <bean id="departmentDao" class="com.taxandtech.lab.wicket.dao.DepartmentDaoImpl">
<property name="sessionFactory" ref="sessionFactory"/>
    </bean>

    <bean id="departmentService" class="com.taxandtech.lab.wicket.service.DepartmentServiceImpl">
<property name="departmentDao" ref="departmentDao" />
    </bean>

     <bean id="wicketApplication" class="com.taxandtech.lab.wicket.web.WicketApplication">
<property name="departmentService" ref="departmentService"/>
    </bean>
</beans>

And that’s about it.You would normally can your spring bean from your wicket page as such:

public class DepartmentInput extends WebPage{
    private Department department;

    public DepartmentInput() {
        add(feedback);
        add( new DepartmentInputForm("departmentInputForm", new CompoundPropertyModel( new Department() )));
        add( new Label("departmentName", new PropertyModel(department, "name" ) ));
    }

    public class DepartmentInputForm extends Form{

        public DepartmentInputForm(String id, final CompoundPropertyModel model) {
            super(id, model);

            department = (Department)model.getObject();

            add(new TextField( "name" ) );

            add(new Button("save"){
                public void onSubmit(){
                    getDepartmentService().save(department);
                }
            });
        }
    }

    protected DepartmentService getDepartmentService(){
        return ((WicketApplication)getApplication()).getDepartmentService();
    }
}

Watch closely on line 19-23 on how the button calls the service and on line 27-29 how the service is called from WicketApplication that we have set up before.

Tags: spring, websphere, wicket

	Ravi on Do we need to unit test Rails…
	Frederick on Creating custom component in S…
	an3m1 on 10 Java Technology Resolution …
	Rafael Ferreira on Using GWT’s Hyperlink…
	Alex on Creating custom component in S…

Joshua Java

Setting up Spring + Wicket on Websphere 5

9 Responses to "Setting up Spring + Wicket on Websphere 5"

Leave a Reply

Pages

Top Posts

Recent Posts

Recent Comments

Flickr Photos

Tags

Joshua Java

Setting up Spring + Wicket on Websphere 5

9 Responses to "Setting up Spring + Wicket on Websphere 5"

Leave a Reply

Pages

Top Posts

Recent Posts

Recent Comments

Flickr Photos

Tags

Category Cloud