dispatch returning 404 not found errors on updating gwtp from 0.6 to 1.0

[yakrider]

Hi all, 

I really tried looking through all forums and posts and double and triple checking my setup so am really looking for some help here.

I have a project that was (and is) working on gwtp 0.6. For exact reproduction of issue, I have set them both up using the gwtp-all packages without maven and in eclipse. 

The two projects are EXACTLY the same except for the following required changes made : 

- gwtp-all-0.6.jar replaced with gwtp-all-1.0.jar (gin and guice are both at gin-2.1 and guice-3.0)

- event bus imports updated to bindery

- all Widget references updated to IsWidget

also note the following changes not made (or they were made, but the problems remained, so were turned back to try and isolate issue)

- in <>.gwt.xml, still inheriting mvp without entry point, and using the entry point setup like was done for 0.6 which still is working

- also, still defining in xml a client ginjector

So this all compiles and loads up, when debugger breakpoints are placed in each of the guice files used (ServerModule, GuiceServletConfig, DispatchServletModule), they are hit and passed through normally at startup (and therefore going through binding of all the actions and handlers)

However, the problem remains that when using 0.6, the actions are routed to the handlers and everything works. On using 1.0, the 404 NOT_FOUND error is returned by the server (and the breakpoints in the action handler are never reached). 

So it seems like something is screwy with how the new dispatch system is setup, or how guice plugs into things etc.. unfortunately, I am not sure how to debug more or get anywhere, I've been about pulling my hair out stuck in this and losing productivity.

I would very much appreciate any help, or pointers on how to get past this, or if this sounds remotely familiar to anyone and what might be causing it. 

Thank you very much, 

I am hoping someone can shed some light !

[André Zimmermann]

Hey there, I had the same issue when I migrated from 0.7 to 1.0.2. 

This what solved my problem and I'm pretty sure is the same issue: https://groups.google.com/d/msg/gwt-platform/B0CilCGDqE4/FO6bk7Qwc4QJ