Skip to content

What is the rationale behind the JSonStAX architecture? #2

Description

@GoogleCodeExporter
The JSON parsing classes seem rather rigid and particularly difficult to debug. 
What was the original design rationale behind using a JSonJacksonStAX model? 
Since much of the code is now obsolete with respect to the AppNexus API, is 
there any reason to maintain it? google-gson, while it uses reflection, is much 
simpler to use and significantly less prone to error.

Original issue reported on code.google.com by brean...@onespot.com on 27 Dec 2012 at 8:41

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions