#1505 new
Jaime Hablutzel

conflicts between play evolutions in existence of a Job with @OnApplicationStart

Reported by Jaime Hablutzel | April 26th, 2012 @ 04:05 PM

Reproduction steps:

If you have a class like this one:

public class SetupClass extends Job {

    public void doJob() {


Then you create an evolution like the following:

# --- !Ups

create table pojo(
    id bigint  not null auto_increment,
    name varchar(255),
    primary key (id)

And you have an action method in a controller like this one:

   public static void index() {
        List<Pojo> fetch = Pojo.find("byName", "foo").fetch();
        String name= fetch.get(0).name;


Then you run play this will warn you that evolutions need to be run, so you run it and inmediately you will get a

ClassCastException occured : models.Pojo cannot be cast to models.Pojo

Assuming you was in localhost:9000 and the action method matched that url. The curious thing is that this error doesn't happen if you don't have any class annotated with @OnApplicationStart,

Debugging I encountered that this is related to the fact that when Evolutions throws play.db.Evolutions$InvalidDatabaseRevision play sets play.Play#started to false making play framework to call play.Play#start again as a result to the next call to play.Play#detectChanges

Framework version: 1.2.x

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.