Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

What is the rationale behind the JSonStAX architecture? #2

Open
GoogleCodeExporter opened this issue Apr 30, 2015 · 0 comments
Open

What is the rationale behind the JSonStAX architecture? #2

GoogleCodeExporter opened this issue Apr 30, 2015 · 0 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

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 [email protected] on 27 Dec 2012 at 8:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter