Well Mike, my problem is not to avoid user from accessing JSP directly, but to show her a list of links with a meaning as a result of a search action. The problem is even worst, if you think that I'm using Tiles, with the actual web content in JSPs which are never accessed directly neither by a Struts action, but imported as defined in the Tiles definition file.
Did anyone realize a search facility which runs on a Struts application running Tiles? How did you solve the problem: content-linkable mappings? I'm thinking to create a configuration file with a mapping between the content JSP pages and meaningful Struts action links. The search facility will return a list of meaningless paths to JSPs containing the actual website content, and a class will search for the Struts mapping between those links and linkable actions. Does it make sense? (here he was looking around with a very interrogative expression...) Marco <!-- ORIGINAL MESSAGE --> From: "Mainguy, Mike" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Subject: RE: Searching facility questions Hide your .jsp files in /WEB-INF/foo (I use /WEB-INF/pages) so that the user cannot navigate directly to them. Alternatively hide them ANYWHERE so they cannot directly link to them. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
