1. move index.jsp to /WEB-INF/index.jsp 2. configure an action called index (in xwork.xml) that uses the com.opensymphony.xwork.ActionSupport class (since it just returns success from execute()) map the success view as a dispatcher type, to /WEB-INF/index.jsp 3. create an empty file called index.action in the root folder of your webapp. 4. configure your servlet container to treat index.action as a 'welcome file' or 'default file' This empty index.action allows the servlet container to see that there is a 'welcome file' there, though the .action mapping makes it use the webwork servlet dispatcher. This causes your action to be automatically triggered as the 'index' action. remigijus wrote:
-- Any damn fool can write code that a computer can understand... The trick is to write code that humans can understand. [Martin Fowler http://www.martinfowler.com/distributedComputing/refactoring.pdf] ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork |
- [OS-webwork] How to prevent access to the index.jsp and othe... remigijus
- Re: [OS-webwork] How to prevent access to the index.jsp... remigijus
- Re: [OS-webwork] How to prevent access to the index.jsp... Rickard Öberg
- Re: [OS-webwork] How to prevent access to the index... Hani Suleiman
- Re: [OS-webwork] How to prevent access to the i... Cameron Braid
- Cameron Braid