Stream API doesn't work without Javassist dependency about java HOT 8 CLOSED

stream api is considered as "optional". 99% percent of time, byte array input will be the best option.

from java.

Guess I am at that 1%. I have to process large json files and it is not possible to load them into the byte arrays held in memory. It should be possible to use streaming and writer API without dynamically linking anything or generating any code at runtime.

from java.

The best option is to make a fork of this library. Delete IterImpl.java and rename IterImplForStreaming.java to IterImpl.java. The idea is to support streaming mode without virtual method call. So Javassist is used to shadow the class in runtime.

from java.

That is pretty much what I had to do, but it is not maintainable like that. I'd have to stick with Jackson if that would be the only option.

As a thought. Maybe make it other way around. Stream by default and replace virtual call when dynamic codegen is used... or provide JsonIteratorStream hardwired with IterImplForStreaming

from java.

how about I maintain the fork for you? like lite version. It is just a bash script to copy the files needed over. What features do you need? Encoding or decoding? Iterator only or more?

from java.

Thank you for a generous offer, but that won't be necessary.
I completed evaluation of Jsoniter. Really like simplicity of the stream API. But I didn't get a significant performance increase over jackson 1.x for my project when parsing large json datasets using stream api. Also jackson is more forgiving when parsing various data types. So I will have to keep my existing implementation.

from java.

switch case based on string field is slow. that is the biggest bottleneck in all the parsing process.

from java.

I still see quite a bit of jsoniter code at the top of the list:

from java.