#1527 new
Igor Bljahhin

Load configuration files from container's classpath

Reported by Igor Bljahhin | May 17th, 2012 @ 08:50 AM | in 1.4.x


I would like to have an option to put the configuration file "application.conf", or the file included into it with @include statement, into the classpath of web server. My use case is described below.

Let's suppose, I released my application and now I pass the released WAR to system administrator. The administrator puts WAR into web server and wants to change some configuration parameters, which are specific for server's environment, like database connection settings. It is better if WAR file will stay unchanged and those settings will be defined somewhere in the web server. The administrator creates the file called "myapp-target.properties" and puts it into web server's classpath (in case of Tomcat 6 it is "lib" folder. My application includes that file into "application.conf" using this statement:


WAR file stays untouched and can be moved as is to production server, when testing is done.

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.