When testing a new RPC interface, you may get the following message when running in hosted mode:
The development shell servlet received a request for 'rpcs/myService' in module 'com.example.RPCExample'
Resource not found: rpcs/myService
<!-- Example servlet loaded into hosted mode tomcat -->
<servlet path ="/myService" class="com.example.server.MyServiceImpl" />
Also make sure that the path attribute in your gwt.xml's servlet tag
matches the url-pattern in your web.xml. These both need to stay in
sync with the URL your client code is requesting.
Hope that helps,
Isaac
On Jan 3, 2008 12:20 AM, Payam <payam...@gmail.com> wrote:
>
The new FAQ looks good. It brings to my mind a possible error-handling
improvement. I see two error cases:
1. There is no <servlet> tag mapping the requested path to a class.
2. The class could not be found.
Would it be too difficult (I haven't looked up the relevant code) to
differentiate the error messages for these two scenarios? In the first
case I suppose there's no way to tell a failed RPC call from a request
for a non-existent static file, but in the second case I imagine
there's something comparable to a ClassNotFoundException that could be
caught and handle separately.