#1207 new
2ch

JPAException when annotating @NoTransaction

Reported by 2ch | November 3rd, 2011 @ 01:33 AM

Framework version: 1.2.3
Platform you're using: Fedora 15 LXDE

Reproduction steps:
Exception happens in the next code:

@NoTransaction
public static boolean uploadNewBase(@Required File base, @Required String separator) throws FileNotFoundException, IOException, SQLException
{
    LineNumberReader lnr = new LineNumberReader(new FileReader(base));
    lnr.skip(Long.MAX_VALUE);
    int count = lnr.getLineNumber();

    if(Tarification.checkAndCharge(Security.getUser().id, 0, count))
    {
        if(separator.isEmpty())
        {
            separator = ";";
        }

        Long user_id = Security.getUser().id;

        BufferedReader br = new BufferedReader(new FileReader(base));

        while(br.ready())
        {
            String readLine = br.readLine();
            String[] split = readLine.split(separator);

            if(split.length > 1)
            {
                String email = split[0], password = split[1];

                Base b = new Base(Security.getUser(), email.trim(), password);

// DB.execute("INSERT INTO bases (user_id,email,password) VALUES (" + user_id + ", '" // + email.replaceAll("'", "\\'") // + "','" + password.replaceAll("'", "\\'") + "')");

                b.save();
            }
        }

        br.close();
        base.delete();

        return true;
    }

    base.delete();

    return false;
}

Details:

The exception is:
play.exceptions.JPAException: The JPA context is not initialized. JPA Entity Manager automatically start when one or more classes annotated with the @javax.persistence.Entity annotation are found in the application.

at play.db.jpa.JPA.get(JPA.java:22)
at play.db.jpa.JPA.em(JPA.java:51)
at play.db.jpa.JPQL.em(JPQL.java:16)
at play.db.jpa.JPQL.find(JPQL.java:44)
at models.User.find(User.java)
at controllers.Security.getUser(Security.java:30)
at controllers.GlobalController.userStat(GlobalController.java:23)
at play.mvc.ActionInvoker.invoke(ActionInvoker.java:502)
at play.mvc.ActionInvoker.invokeControllerMethod(ActionInvoker.java:476)
at play.mvc.ActionInvoker.invokeControllerMethod(ActionInvoker.java:471)
at play.mvc.ActionInvoker.handleBefores(ActionInvoker.java:320)
at play.mvc.ActionInvoker.invoke(ActionInvoker.java:140)
at Invocation.HTTP Request(Play!)

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.

People watching this ticket

Pages