Actually, it's simpler than that (as I just saw on another thread). Just
implement unspecified() in your action to override the default behaviour
when no dispatch method is provided.

Paul

> -----Original Message-----
> From: Paul McCulloch [mailto:[EMAIL PROTECTED]
> Sent: 24 March 2004 18:49
> To: 'Struts Users Mailing List'
> Subject: RE: blocking bookmarked actions
> 
> 
> The way I achieved this was to extend ActionServlet so that a 
> GET or POST
> parameter was added to the request, and extended 
> RequestProcessor to deal
> with the get's differently.
> 
> If you just need to catch calls to dispatch actions without a 
> method then
> override execute() in your base DispatchAction class.
> 
> Paul
> 
> > -----Original Message-----
> > From: Mark Shifman [mailto:[EMAIL PROTECTED]
> > Sent: 24 March 2004 18:32
> > To: Struts Users Mailing List
> > Subject: Re: blocking bookmarked actions
> > 
> > 
> > where do I do the blocking?  The action I am having problems 
> > with is a 
> > LookupDispatchAction and I get this kind of error message
> > 
> > javax.servlet.ServletException: Request[/RechartFiles] does 
> > not contain handler parameter named method
> >     
> > org.apache.struts.actions.LookupDispatchAction.execute(LookupD
> > ispatchAction.java:199)
> > 
> > ...
> > 
> > Paul McCulloch wrote:
> > 
> > >You code code your app to always use http POST, but block 
> > GETs. This may not
> > >be suitable if you've already written the app though!
> > >
> > >Paul
> > >
> > >  
> > >
> > >>-----Original Message-----
> > >>From: Mark Shifman [mailto:[EMAIL PROTECTED]
> > >>Sent: 24 March 2004 18:17
> > >>To: Struts Users Mailing List
> > >>Subject: blocking bookmarked actions
> > >>
> > >>
> > >>Suppose someone bookmarked an action such as 
> > >>/yourhost/yourapp/someAction.do and you really want them 
> to only go 
> > >>through the html pages.
> > >>
> > >>How do your block or catch these actions and redirect them to the 
> > >>appropriate place?
> > >>
> > >>mas
> > >>
> > >>
> > >>------------------------------------------------------------
> > ---------
> > >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > >>
> > >>    
> > >>
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> **************************************
> Axios Email Confidentiality Footer
> Privileged/Confidential Information may be contained in this 
> message. If you are not the addressee indicated in this 
> message (or responsible for delivery of the message to such 
> person), you may not copy or deliver this message to anyone. 
> In such case, you should destroy this message, and notify us 
> immediately. If you or your employer does not consent to 
> Internet email messages of this kind, please advise us 
> immediately. Opinions, conclusions and other information 
> expressed in this message are not given or endorsed by my 
> Company or employer unless otherwise indicated by an 
> authorised representative independent of this message.
> WARNING:
> While Axios Systems Ltd takes steps to prevent computer 
> viruses from being transmitted via electronic mail 
> attachments we cannot guarantee that attachments do not 
> contain computer virus code.  You are therefore strongly 
> advised to undertake anti virus checks prior to accessing the 
> attachment to this electronic mail.  Axios Systems Ltd grants 
> no warranties regarding performance use or quality of any 
> attachment and undertakes no liability for loss or damage 
> howsoever caused.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to