I just used this web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<web-app>

  <context-param>
     <param-name>org.restlet.application</param-name>
     <param-value>play.json.TestApplication</param-value>
  </context-param>

        <listener>
                
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
        </listener>


        <servlet>
                <servlet-name>shell</servlet-name>
                
<servlet-class>com.google.gwt.dev.shell.GWTShellServlet</servlet-class>
        </servlet>

        <servlet>
                <servlet-name>jsonServlet</servlet-name>
                <servlet-class>play.json.JsonServlet</servlet-class>
        </servlet>


  <servlet>
     <servlet-name>RestServlet</servlet-name>
     
<servlet-class>com.noelios.restlet.ext.servlet.ServerServlet</servlet-class>
  </servlet>

        
        <servlet-mapping>
                <servlet-name>shell</servlet-name>
                <url-pattern>/*</url-pattern>
        </servlet-mapping>

        <servlet-mapping>
                <servlet-name>jsonServlet</servlet-name>
                <url-pattern>/jsonServlet/*</url-pattern>
        </servlet-mapping>

  <servlet-mapping>
     <servlet-name>RestServlet</servlet-name>
     <url-pattern>/api/v1/*</url-pattern>
  </servlet-mapping>

</web-app>

But I must admit I never tested using the GWT-RPC. I only use restlet calls.

On 9/3/07, Rob Heittman <[EMAIL PROTECTED]> wrote:
>
> Just thought I would post this to the list because I hadn't seen it
> documented anywhere else.
>
> In Hosted Mode, the configuration of Google Web Toolkit is optimized to
> facilitate use and testing of its own RPC mechanism.  We have GWT
> applications, but do not use GWT-RPC, since we have flexible server services
> using the REST style and now Restlet.  GWT clients are only one of many
> possible consumers of the server-side REST services.  Anyway, after starting
> to adopt Restlet, we found the Restlet+GWT Hosted Mode combination tricky to
> get to work in any straightforward way, largely due to path reporting
> problems in GWT's embedded copy of Tomcat.
>
> The briefest solution we found (if not the cleanest) was to subclass
> Restlet's ServerServlet to cause it to manage and invoke the GWTShellServlet
> directly, as attached, and then register this in place of GWTShellServlet in
> the Hosted Mode working directory.
>
> Happy to hear better solutions, and hope that anybody trying to do this
> integration in the future finds this thread.
>
> - Rob
>
>
>

Reply via email to