#26 ✓resolved
Erwan Loisant

Allow other formats when binding parameters

Reported by Erwan Loisant | October 5th, 2010 @ 11:56 AM | in 1.1

In case of a resource url, users can bind define binding on date.

/document/${documentDate} ie /document/01-12-2009/ (documentDate might be the Id)

However, currently we cannot specified the date format and we cannot retrieve the date format according to the locale:
the URL of any resources should not change depending of the locale.

http://groups.google.com/group/play-framework/browse_thread/thread/...

Add a new annotation that allows to specify the date format: @As("dd-MM-yyyy")

for example:

public static show(@As("dd-mm-yyyy") Date date) {

...

}

Note that the same kind of annotation could be used in another use case:

/mailboxes/{<.*>folderNames}/ -> /mailboxes/2009/june/

and then

public static show(@Separator("/") List mailboxes) {

...

}

or

/books/{languages}/ -> /books/fr,ja,de/

public static show(@Separator(",") List mailboxes) {

...

}

This is basically the same idea, and thus means that the mechanism must be flexible.

Imported from Launchpad: https://bugs.launchpad.net/play/+bug/458450

No comments found

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