#1158 ✓duplicate

Error parsing JSON

Reported by Rudy | October 12th, 2011 @ 07:24 AM | in 1.2.4 (closed)

Framework version: 1.2.x (SHA1 ID b6ed01cd...)
Platform you're using: OSX 10.6, chrome 14.0.835.202, Java version 1.6.0_26

Reproduction steps:
send a JSON object from the controller to the browser. (event.publish)
Set a JavaScript breakpoint at the websocket.onmessage line.
You will see the message successfully delivered by the websocket.
now in the JS console, upon querying the object we get "{"message": "hello"}"
whereas to successfully parse the JSON, the expected format is '{"message": "hello"}'
$.parseJSON('{"message": "hello"}'); successfully yeilds an object whereas
$.parseJSON("{"message": "hello"}"); throws an exception "Unexpected Token"

The JSON object sent down to the browser is surrounded by double quotes whereas the library is expecting to see the JSON object surrounded by single quotes.
When using chrome 12 with play version 1.2.3, the JSON is able to successfully able to parse.

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.


Referenced by