#1479 ✓invalid
Dmitriy Kanaev

Only default JPA is configured in multi-db configuration.

Reported by Dmitriy Kanaev | April 2nd, 2012 @ 07:48 PM | in 1.3 (closed)

Framework version: master(playframework-play-1.1-1102-g6b5319536edcb5039a8982ae3b854eb7a485733a)
Platform you're using: Windows 7 x64

Reproduction steps: Please see attached file multidb-test.zip

In general the steps are:
1. Create configuration for several databases
2. Create any model annotated with @Entity to force JPA to start
3. Try to getJPAConfig("conf_name"). It fails. Is it expected behavior ?


System.out.println("Default db name: " + DB.getDBConfig());
System.out.println("Name of the second db: " + DB.getDBConfig("localhost"));
System.out.println("Default JPA(play): " + JPA.em());
System.out.println("Another(from 'localhost' db name) JPA(play): " + JPA.getJPAConfig("localhost"));

Results in:
Default db name: play.db.DBConfig@ec32de
Name of the second db: play.db.DBConfig@ffab0a
Default JPA(play): org.hibernate.ejb.EntityManagerImpl@1c26db4

14:52:27,727 ERROR ~
.... JPA error
A JPA error occurred (No JPAConfig is found with the name localhost):

Also in documentation we can find an example:
EntityManager em = JPA.getJPAConfig("other").em();

In practice JPAConfig does not have em() method.

And this link http://www.playframework.org/documentation/1.2.3/jpa tells about multi-db feature. But Play 1.2.3 does not have it.

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.