i got the same problem i guess... read this: "Templates of type: "servlet"; no longer work in 3.5.8"
so i am interested in a solution ;) thx for the bypass hint... it is not a good solution, but if nothing helps ;) greetings rainer Magnolia - User mailing list wrote: > > Hello all, > > For one of our clients, we developed some custom Spring servlets to > integrate Magnolia content created by the client with a Spring driven > webapp that we'd already developed for them. These servlets were > developed for Magnolia 3.0.1, where we just set them up as regular > servlets in the web.xml and added the node > /server/unsecureURIList/client with the URI of our Spring based pages, > /.magnolia/client/*. All the Spring JSPs, which in the old webapp used > to live in /WEB-INF/jsp (where users could not access them directly), > were relocated to the location of our custom module's template files in > /templates/client-mgnl/spring/jsp. > > Now that we are upgrading to 3.5.4, I have had to set up the servlets in > the /server/filters/servlets node. Everything seems to be working fine. > The Spring based servlet has a mapping of /.magnolia/client/*.do and > requests like /.magnolia/client/page.do are going through this servlet. > Spring does all its custom stuff, but when it goes to render the view, > it can't seem to access the JSP pages in the > /templates/client-mgnl/spring/jsp area. The page ends up rendering as a > 404 page with the error message > "/templates/client-mgnl/spring/jsp/page.jsp not found on this server." > > After much trial and error, I discovered that the pages will render > perfectly if I add a bypass to the "cms" servlet for > /templates/client-mgnl/spring/jsp similar to the ones for docroot, etc. > However, this leaves my JSPs that are in that directory accessible to > the outside world, and while it's unlikely that someone would find those > pages (and they don't even work anyway when accessed directly), I don't > like to expose the templates directory. > > I feel like I must be missing some new setting that I can make that will > allow my Spring servlet to access the JSPs in the templates directory > without me exposing that directory to the world. Does anyone have any > suggestions for what I could set other than bypassing Magnolia for the > templates directory? > > Thanks! > Miranda > > > -- > Miranda Jones > Objective Consulting, Inc. > http://www.spiders.com > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- > > -- View this message in context: http://www.nabble.com/Magnolia-3.5.4%3A-Custom-servlet-error-tp15748577p18717129.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
