Solved.. I'm not sure I wanna know why - because this looks like one of the infamous undocumented OC4J "features" - but we fixed it by adding a file to the root folder of our web app (for instance src/main/webapp/ index.html if you’re using the default maven project layout).
(Thanks to http://www.andrejkoelewijn.com/wp/2009/11/04/wicket-and-mule-on-oc4j/) So this is not Guice related at all. It's Oracle (what else...). Guido On Dec 10, 4:51 pm, Helmers <[email protected]> wrote: > Hi, > > we introduced the Guice Servlet Extensions in our Guice application. > It works fine in Jetty, but in OC4J we are getting the message " > Forbidden - You don't have permission to access /huisbezoek/ on this > server". > > I rememember that are similar issues around Wicket; they recommend > using the WicketServlet instead of WicketFilter when deploying in OC4J > (version 10.1.3). > > We are using Wicket by the way (we bind the WicketServlet in the > ServletModule that is added to the injector in the > GuiceServletContextListener; all > conformhttp://code.google.com/p/google-guice/wiki/Servlets). > But I think the problem is not related to Wicket but to the > combination of the filter mapping from /* to the GuiceFilter and the > fact that it's deployed in OC4J. The mapping /* -> GuiceFilter is the > only filter or servlet mapping we define in web.xml, so if the filter > "doesn't work" there's no active URL mapping at all... explaining to > the Forbidden message... > > So I am wondering: Did anyone successfully deploy a Guice application > with a ServletModule in OC4J? If so, did you use the GuiceFilter? Is > there an alternative for the GuiceFilter (like the WicketServlet in > the Wicket world)? > > Thanks, > Guido -- 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.
