Note that json.org is a spec, not an implementation. Gary
On Wed, Apr 10, 2013 at 2:13 PM, Daniel Pitts <[email protected]>wrote: > Do you mean "a common way" or "the Commons way". json.org is pretty much > canonical when it comes to JSON encoding. How much more common do you need? > I realize that this is the apache commons user list, and it wouldn't hurt > to have Commons support JSON better. However as an pragmatic engineer, I > would use json.org before asking the apache community to duplicate that > functionality, unless there are issues with licensing for you. I don't know > off the top of my head what license json.org uses. > > On 4/10/13 2:37 AM, Maurizio Cucchiara wrote: > >> Actually, when I was talking about the best way, I was asking for a >> "common" way. >> >> On 10 April 2013 02:39, Daniel Pitts <[email protected]> wrote: >> >>> I might suggest looking into the json.org library. >>> >>> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > user-unsubscribe@commons.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > > -- E-Mail: [email protected] | [email protected] JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
