#726 new

Bug Validation: error has bad fieldname for empty entity

Reported by Cyrille37 | April 13th, 2011 @ 01:21 PM

Not easy to find a short way to explain the problem (bug ?).

It's about the edition of a list of object. In the view I put existing list items and add some empty list items to facilitate the addition of new items. I manage the state of those new object in the contoller.save(). All stuff work fine except the field.name needed to print errors.

For new items (Entity with no Id), the validation process change the field name from the second new field, like :

p0 is an existing entity field, where p1 and p2 are not exists entities, they were added by hand to the list before rendering.

p0.name: Minimum size is 2
p0: Validation failed
p1.name: Minimum size is 2
p1: Validation failed
p1.p2.name: Minimum size is 2
p2: Validation failed

See that p2.name become "p1.p2.name". So, the view could not retrieve the p2's name field.

I join a simple case: the controller, the view, the entity, the initial data.

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



Referenced by