Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Case problem in JSon conversion
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
James Roper  
View profile  
 More options Oct 8 2012, 11:39 pm
From: James Roper <jrop...@gmail.com>
Date: Mon, 8 Oct 2012 20:39:18 -0700 (PDT)
Local: Mon, Oct 8 2012 11:39 pm
Subject: Re: [2.0.3] Case problem in JSon conversion

This has everything to do with the complexities of the Java bean naming
conventions, and Jackson trying to guess what you want.  Play is simply
using Jackson, so just annotate your property with @JsonProperty("uForWin")
to explicitly map it.

On Tuesday, 9 October 2012 02:18:08 UTC+11, Xavier wrote:

> Hi,

> I have an object with the attribut "uForWin".

> In my controller, I have this code to return the object as JSon object for
> JavaScript use :

> play.libs.Json.toJson(object)

> In client slide, in JavaScript, the JSON object has 2 properties with the
> orinigal value of uForWin : uForWin and uforWin.

> My object has other attribute and I don't have this problem for them. If I
> rename this attribute, I never have the problem. Seems to be linked to the
> single lowercase character at the beginning of the Java attribute.

> Any idea or explanation ?

> Thanks,

> Xavier


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.