Has anyone successfully configured Stripes through the ServletModule?
I have experienced two different issues:

1. When I set up Stripes completely in ServetModule, I get the
following error on Jetty (a similar error shows for Resin, so it does
not seem to be a container-specific issue).  The requested URL is "/
app/category/blah".  It is mapped to a Stripes ActionBean which should
forward the request to a JSP.  This works fine in web.xml.

2010-09-18
13:22:47.536:WARN:org.apache.jasper.servlet.JspServlet:PWC6117: File
"MY_EXPLODED_WAR_DIR/app/category/blah" not found


2. Because I couldn't get Stripes to work in ServletModule, I tried
mixing some ServletModule filter() bindings with the legacy Stripes
mappings still in web.xml.  This approach almost works, but the
following Stripes servlet mapping in web.xml seems to prevent Guice
from picking up the /app/* filter pattern.  I have no idea why, but if
I remove it, Guice starts filtering /app/* again.

    <servlet-mapping>
        <servlet-name>StripesDispatcher</servlet-name>
        <url-pattern>/app/*</url-pattern>
    </servlet-mapping>

I'm mapping GuiceFilter to "/*" in web.xml.  And I have the following
in my ServletModule:

        bind(MyFilter.class).in(Singleton.class);
        filter("/app/*").through(MyFilter.class);

Note: Mapping a filter to "/*" in ServletModule will still work; it's
just the "/app/*" mapping that has problems.

-- 
You received this message because you are subscribed to the Google Groups 
"google-guice" 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-guice?hl=en.

Reply via email to