#1690 confirmed
Igmar Palsenberg

@Before, @After, @Finally

Reported by Igmar Palsenberg | August 12th, 2013 @ 09:38 AM | in 1.4.x

The @Before, @After and @Finally controller annotation depend internally on the whole package name. That means that
when having a :

package a.b.c;
public class A extends Controller {

@Before(only = { "check" } protected static void checkCookie() { ..... } }

package c.d.e;
public class B extends Controller {
public static void check() { // Won't trigger, since the before is package-checked to match a.b.c } }

the @Before doesn't trigger.

Framework version: 1.2.6, 1.2.x git

Platform you're using: OSX, Linux

Reproduction steps:


We need a wat to tell the annotations that it should ignore to package name, so we can use it in subclassed controllers that are in a different package.

I'll do a pullrequest with a proposed fix.

Comments and changes to this ticket

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.