#1245 new

Allow specification of default timezone in application.conf

Reported by santos | November 13th, 2011 @ 10:59 AM

There are several options to specify the default timezone in Play! such as:

  • Programmatically set the default timezone in a bootstrap job
  • Pass JVM option -Duser.timezone to java command line

This could be achieved in a simpler way by allowing the default timezone to be specified in application.conf (no need to set it programmatically and independent of command line options), in a similar way to what is already done with e.g. configuration option jvm.memory.

Framework version: 1.2.3
Platform you're using: Linux

Comments and changes to this ticket

  • santos

    santos November 20th, 2011 @ 09:53 AM

    If this feature is to be implemented - I find it useful - it should be the equivalent of passing JVM option -Duser.timezone to Java command line and not the equivalent of setting the timezone in a bootstrap job.

    Setting the timezone in a bootstrap job may cause problems with Log4J and JVM/DB date/time values translation. My guess is that these problems are caused by the fact that Log4J and the MySQL driver are loaded before the bootstrap job. For more details on these issues, see my e-mail "Play! application using UTC - how to do it and how not to do it".

  • Greg Beyer

    Greg Beyer January 9th, 2018 @ 01:38 PM

    I don’t know that through this process we can set the default time zone in the application. Thank you so much for your cheap assignment help uk guidance and statistics. I am truly impressed with your working. Smart really smart you are.

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