#1098 new

@before annotated method, "request.params" doesn't have the form "post" params

Reported by ahmed | September 5th, 2011 @ 10:32 PM

@before annotated method, request.params doesn't have the form "post" params

Framework version: 1.2.1
Platform you're using: netbeans 6.9.1 on windows 7

Reproduction steps: make a form with method "post", and make an @before annotation before its action, in this @before annotated method try to get "request.params" the data in it will not contain the data of the form, also the boolean called requestIsParsed is false. I don't know this might help.
meanwhile, for the forms with method "get", its data will be in the request.params

a little note:
I made a parent controller for all my controllers, and in this parent controller I made the @before annotation like this:

public static void doSomehting() {
    //this is the problem "abc", <input name="abc"/> inside form with method "post", but in request.params it is not found
    if (request.params._contains("abc")) {    
        //tell me

by the way "abc" will be in request.params in the action itself not in the @before annotation.

sorry for this next question:

@before(only={"method1", method2})

doesn't work in the parent controller i discussed earlier i need to check myself like:

if (request.actionMethod.equals("search") || request.actionMethod.equals("browse")) {}

how to make the "only" work??

No comments found

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Referenced by