UPDATE: see this post for a complete working example of GWT integrated with stripes.

GWT is a really nice toolkit for building javascript based user interfaces - without the need for writing javascript. Check it out if you have not yet. GWT ships with a servlet (called RemoteServiceServlet) that should be used for the RCP (remote procedure call) parts of GWT.
But as my current web framework of choice is Stripes this servlet was of no specific use for me. Thanks to the Stripes mailing list the following abstract ActionBean implementation arised: package de.wemwannwas.web; import java.util.Enumeration; import java.util.NoSuchElementException; import javax.servlet.ServletConfig; import javax.servlet.ServletContext; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import net.sourceforge.stripes.action.ActionBean; import net.sourceforge.stripes.action.ActionBeanContext; import net.sourceforge.stripes.action.DefaultHandler; import net.sourceforge.stripes.action.Resolution; import com.google.gwt.user.server.rpc.RemoteServiceServlet; /** * Abstract actionBean, needed for the RPC backend part of GWT * * @author Kai Grabfelder (nospam@kaigrabfelder.de) * */ public abstract class AbstractGoogleWebToolkitActionBean extends RemoteServiceServlet implements ActionBean { private static final long serialVersionUID = 1L; private ActionBeanContext context; @DefaultHandler public Resolution defaultHandler() { return new Resolution() { public void execute(HttpServletRequest request1, HttpServletResponse response1) throws Exception { doPost(request1, response1); } }; } public ActionBeanContext getContext() { return context; } public void setContext(final ActionBeanContext context) { this.context = context; // GWT servlet needs to be initialized with the servletConfig - // otherwise it can't access the servletContext try { super.init(new ServletConfig() { public String getInitParameter(String name) { return null; } public Enumeration<?> getInitParameterNames() { return new Enumeration<String>() { public boolean hasMoreElements() { return false; } public String nextElement() { throw new NoSuchElementException(); } }; } public ServletContext getServletContext() { return context.getServletContext(); } public String getServletName() { return AbstractGoogleWebToolkitActionBean.class.getName(); } }); } catch (ServletException e) { throw new RuntimeException(e); } } } Now I can create implementations of this ActionBean - and let them implement my ServiceInterfaces - just like described in the GWT guide. Here is such an implementation example: /** * ActionBeans that servers as a service endpoint for all GWT based parts of * kinokai.de * * @author Kai Grabfelder (kai.grabfelder@kinokai.de) */ @UrlBinding(value = "/ajax/index.htm") @Secure(roles = { Groups.MEMBER }) public class GoogleWebToolkitActionBean extends AbstractGoogleWebToolkitActionBean implements IGoogleWebToolkitService { @SpringBean private IAnotherService anotherService; public String myMethod(String foo){ return anotherService.myMethod(foo): } } Maybe there are more elegant ways of doing this but it works for me now. Or how have you integrated GWT with stripes? Leave a comment!!!

Responses[9]

Posted by Kai Grabfelder on July 12, 2007 8:36:00 PM CEST # Attachment