there is no file system in gae so
the multipart wrapper could be your problem.
it probably would work locally by not in prod

On May 15, 8:30 am, Mike Lawrence <[email protected]> wrote:
> sorry you're having problems.
> dont think this is an app engine issue
> since many folks use stripes on gae.
> here are the stripe parts from my web XML
>
> <?xml version="1.0" encoding="utf-8"?>
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>         xmlns="http://java.sun.com/xml/ns/javaee"; xmlns:web="http://
> java.sun.com/xml/ns/javaee/web-app_2_4.xsd"
>         
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaeehttp://java.sun.com/xml/ns/javaee/web-app_2_4.xsd";
>         version="2.4">
>
>         <filter>
>                 <filter-name>StripesFilter</filter-name>
>                 <filter-class>net.sourceforge.stripes.controller.StripesFilter
>                 </filter-class>
>
>                 <init-param>
>                         <param-name>MultipartWrapperFactory.Class
>                         </param-name>
>                         
> <param-value>com.wordpong.app.stripes.EmptyMultipartWrapper
>                         </param-value>
>                 </init-param>
>
>         </filter>
>
>         <filter-mapping>
>                 <filter-name>StripesFilter</filter-name>
>                 <servlet-name>DispatcherServlet</servlet-name>
>                 <!-- add jsps for layout support -->
>                 <url-pattern>*.jsp</url-pattern>
>                 <dispatcher>REQUEST</dispatcher>
>                 <dispatcher>FORWARD</dispatcher>
>         </filter-mapping>
>
>         <!-- Stripes Config -->
>         <servlet>
>                 <servlet-name>DispatcherServlet</servlet-name>
>                 
> <servlet-class>net.sourceforge.stripes.controller.DispatcherServlet
>                 </servlet-class>
>                 <load-on-startup>1</load-on-startup>
>         </servlet>
>         <servlet-mapping>
>                 <servlet-name>DispatcherServlet</servlet-name>
>                 <url-pattern>*.action</url-pattern>
>         </servlet-mapping>
>
>         <filter>
>                 <filter-name>DynamicMappingFilter</filter-name>
>                 <filter-
> class>net.sourceforge.stripes.controller.DynamicMappingFilter
>                 </filter-class>
>         </filter>
>         <filter-mapping>
>                 <filter-name>DynamicMappingFilter</filter-name>
>                 <url-pattern>/*</url-pattern>
>                 <dispatcher>REQUEST</dispatcher>
>                 <dispatcher>FORWARD</dispatcher>
>         </filter-mapping>
>
> On May 14, 11:05 am, Pauli Savolainen <[email protected]>
> wrote:
>
>
>
> > Hello
>
> > I had some time to try this again, but I still have no success.
>
> > I have an ActionBean with @UrlBinding("/home"). The @DefaultHandler method
> > ForwardResolutions to index.jsp which only prints "Hello":
>
> > @DefaultHandler
> > public Resolution home() {
> >   return new ForwardResolution("index.jsp"); // Also tried "/index.jsp"
>
> > }
>
> > In dev environment I access my app 
> > viahttp://localhost:8888/index.jspandhttp://localhost:8888/home. Both print 
> > "Hello". That is, it works perfectly.
>
> > After I have deployed my app on appengine I access the application via
> > http://<myapp>.appspot.com/index.jsp. This prints "Hello", but when I access
> > my app via http://<myapp>.appspot.com/home I get an infinite redirect loop.
> > I checked the app engine logs:
>
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/inde 
> > x.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp 
> > /index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp/index.jsp
> > /home/index.jsp/index.jsp
> > /home/index.jsp
> > /home/
>
> > I consider this more an app engine issue than Stripes issue because
> > everything works locally but not in app engine. Stripes uses a servlet
> > filter to handle the UrlBindings. The filter javadocs states:
>
> > This filter takes the following approach to determining when to dispatch an
> > ActionBean<http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/s...>:
>
> >    1. Allow the request to process normally, trapping any HTTP errors that
> >    are returned.
> >    2. If no error was returned then do nothing, allowing the request to
> >    complete successfully. If any error other than 404 was returned then send
> >    the error through. Otherwise ...
> >    3. Check the 
> > ActionResolver<http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/s...>to
> >  see if an
> >    
> > ActionBean<http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/s...>is
> >  mapped to the URL. If not, then send the
> >    404 error through. Otherwise...
> >    4. Invoke 
> > StripesFilter<http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/s...>and
> >    
> > DispatcherServlet<http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/s...>
>
> > So it expects a 404. This all seems like the app engine doesn't like this
> > behaviour, thus the infinte redirect loop.
>
> > I have tried to clean my configuration as much as possible:
> > - I only define the DynamicMappingFilter in my web.xml. No StripesFilter
> > anymore. According to the Stripes documentation this is perfectly ok.
> > - I also had Guice stuff in my web.xml but I removed them as well.
> > - I also configured Stripes to use my own empty implementation of the
> > MultipartWrapperFactory.
>
> > I am running out of ideas. Would be nice if could be confirmed that this
> > error indeed is reproducable and not just my misconfiguration.
>
> > Thanks
> > Pauli Savolainen

-- 
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to