Skip to main content

Return to Answer

Jacksons Wiki link seems to be broken. So I added its git hub page to save next user some time
Source Link
edit approved Feb 25, 2015 at 11:12
Yogi Valani
edit approved Feb 25, 2015 at 11:12
Yogi Valani
  • 481
  • 3
  • 11

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson (Github) -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson (Github) -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer
updated genson on github now
Source Link
reevesy
reevesy
  • 3.5k
  • 1
  • 28
  • 23

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • GensonGenson -- functionality similar to Jackson, aimed to be easier to configure by developer

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer
added genson
Source Link
StaxMan
StaxMan
  • 117k
  • 35
  • 215
  • 241

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

Oddly, the only decent JSON processor mentioned so far has been GSON.

Here are more good choices:

  • Jackson -- powerful data binding (JSON to/from POJOs), streaming (ultra fast), tree model (convenient for untyped access)
  • Flex-JSON -- highly configurable serialization

EDIT (Aug/2013):

One more to consider:

  • Genson -- functionality similar to Jackson, aimed to be easier to configure by developer
Source Link
StaxMan
StaxMan
  • 117k
  • 35
  • 215
  • 241