Hey all,
I managed to solve it by adding Guice into the FORWARD dispatch chain
as well. In dev mode, the blobstore service uses
RequestDispatcher.forward() rather than an HTTP request:
<filter-mapping>
<filter-name>guiceFilter</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>guiceFilter</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>FORWARD</dispatcher>
</filter-mapping>
On Jun 30, 4:39 pm, Matt Mastracci <matt...@mastracci.com> wrote:
> Hi all,
>
> I'm running into an issue on the Dev AppServer where the redirect
> after blob upload doesn't work. I get a 404 error from Jetty when the
> upload completes, even though the URL is valid outside of the upload
> request.
>
> I believe this is because Guice handles all of the serving itself from
> a GuiceFilter, not from servlet bindings. The same code works fine on
> the production AppEngine.
>
> Our web.xml file isn't much more than this:
>
> <filter>
> <filter-name>guiceFilter</filter-name>
>
> <filter-class>com.google.inject.servlet.GuiceFilter</filter-class>
> </filter>
>
> I believe that the Dev AppServer isn't correctly calling back through
> the filter chain after the upload happens.
>
> Thanks,
> Matt.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
