Very nice to have such activity. As I see There is no simple answer. The question I rised only because I couldn't manage to get access to session component from jsp scriplet. I thought, maybe it will be easier to do evrything througout the action, and get access to the component by getting it from ognl value stack. But now I see that I was wrong.
Maybe anyone can give me a hint how to get a session component from jsp sciriplet, or servlet whatever. Note without using ww2 tag. Thanks. ----- Original Message ----- From: "Jamie McCrindle" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 18, 2003 4:36 PM Subject: RE: [OS-webwork] How to prevent access to the index.jsp and other *.jsp files depends on the vendor. resin 2.1.* does it once per request, regardless of how many forwards or includes. weblogic 6.* does it on the request and every forward and every include. > -----Original Message----- > From: Cameron Braid [mailto:[EMAIL PROTECTED] > Sent: 18 December 2003 14:16 > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] How to prevent access to the index.jsp and > other *.jsp files > > > > so if you call requestDispatcher.forward(request,response) or > requestDispatcher.include(request,response), the filter doesn't get > executed again ? > > That is strange, since I though there was a pattern to stop > the second > dispatch from executing the filter again. > > Cameron. > > Hani Suleiman wrote: > > > Due to the incompetence on the part of certain vendors on the 2.3 > > expert group, they couldn't manage to have filters invoked through > > action dispatchers performing well, so the 2.3 spec says a filter > > should only be invoked once per request, > > > > On Dec 18, 2003, at 9:06 AM, Cameron Braid wrote: > > > >> Ok.. I didn't realise that. > >> > >> One thing that you could do is create a > DirectAccessBlockingFilter ;) > >> > >> The name says it all ;) > >> > >> You will have to configure this filter to be 'once per request' so > >> that it only blocks access during the first request dispatch, > >> allowing subsequent dispatches (from the webwork servlet > dispatcher) > >> to access the JSP pages. > >> > >> You can then just map this filter to the extensions you > want to protect. > >> > >> Cameron > >> > >> > >> > >> BOGAERT Mathias wrote: > >> > >> The approach by Rickard doesn't work on some application servers. > >> So do a test before you decide to move everything. > >> > >> Cheers, > >> Mathias > >> > >> -----Original Message----- > >> From: Rickard Öberg [mailto:[EMAIL PROTECTED] > >> Sent: donderdag 18 december 2003 14:55 > >> To: [EMAIL PROTECTED] > >> Subject: Re: [OS-webwork] How to prevent access to the > index.jsp and > >> other > >> *.jsp files > >> > >> > >> remigijus wrote: > >> > >> > >> Hi > >> > >> How can I prevent client form ditect access to any jsp page. I want > >> all > >> pages to be accessed only after action action process. > >> > >> Put them under /WEB-INF/ e.g. /WEB-INF/myapp/someform.jsp > >> > >> /Rickard > >> > >> > >> > >> > >> ------------------------------------------------------- > >> 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 > >> > >> > >> ------------------------------------------------------- > >> 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_id78&alloc_id371&op=click > >> _______________________________________________ > >> Opensymphony-webwork mailing list > >> [EMAIL PROTECTED] > >> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >> > >> > >> > >> > >> > >> -- > >> 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 > > > > > > > > ------------------------------------------------------- > > 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_id78&alloc_id371&op=click > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > -- > 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 ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________ ------------------------------------------------------- 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_id78&alloc_id371&op=ick _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- 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
