Skip to content
Jim Earley edited this page Mar 5, 2021 · 4 revisions

JSON-JEP was created out an itch to address big data problems with JSON data. Most processors require that JSON documents must be loaded into memory before you can process the data. As with XML, big files have always been a limiting factor. First came the Simple API for XML (SAX). The approach is to let the underlying parser send back events as it traverses the XML document, e.g., startElement, startDocument, or endDocument. It's up to a ContentHandler implementation to process these events in manner that fits the intended solution.

The JEP API can be found in the org.ghotibeaun.json.parser.jep package.

In addition to JEP, there is a standard JSON Object Model that can be used to parse JSON documents, which can be found in the org.ghotibeaun.json package. Here you can instantiate new parsers and documents for use in a more traditional environment.

There is also a basic integration the json-path API that works with the native JOM implementation.

Test

Clone this wiki locally