Thanks, guys.
I agree it is easily done with an Interceptor.
But I suspect this is a commonly used feature, and you pretty much need it
to do HTTP right. I hope this gets included in Stripes core or in one of
the other common Stripes libraries.
Cheers,
Sonny
On Thu, Dec 29, 2011 at 3:18 PM, Janne Jalkanen <janne.jalka...@ecyrd.com>wrote:
>
> Since this is probably like a common thing that most of us have to do at
> some point, would it be possible to have it as a feature on Stripes
> directly?
>
> Would be glad to contribute a patch if someone specs how it should
> look-n-work.
>
> /Janne
>
> On Dec 29, 2011, at 15:57 , Mike McNally wrote:
>
> > In my application I have an Intercept that checks, among other things,
> > for an annotation (@ForMethod("post")) on the action bean or event
> > method. (The annotation is one I wrote and not part of Stripes.)
> >
> > On Thu, Dec 29, 2011 at 7:34 AM, Sonny Gill <sonny.pub...@gmail.com>
> wrote:
> >> Hi guys,
> >>
> >> What is the Stripes approach to restricting action invocation by HTTP
> >> method?
> >> For example, if I want to restrict my ItemEdit or ItemDelete action to
> only
> >> be invoked by HTTP POST method.
> >>
> >> Cheers,
> >> Sonny
>
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
