Ankit Garg wrote:As a quick check, can you put a println statement in the retrieveInterstepDataFromJobContext to make sure it is being called...
Junilu Lacar wrote:Since your description of the problem is vague, you're going to get a vague suggestion to fix it.
![]()
I would work on isolating the tests more and doing more localized setup. Also, what you've written may not actually be unit tests. See the criteria that Michael Feathers sets for unit tests.
Stephan van Hulst wrote:Never had much problems with it myself. I have some experience with Jackson and GSON. Can you show what you have tried so far, and what problems you're experiencing?
Jeff Verdegan wrote:
Chris Creed wrote:
Jeff Verdegan wrote:What do you mean "none that are native"?
Perhaps I'm using the wrong term. What I mean is that I can't type in say JSONParser parser = new JSONParser(); into Eclipse an it'll say "hey you're missing java.io.JSONParser. Want me to add that for you?", but instead it seems that a 3rd party choice is needed to be added.
Ah, okay. What you mean then is that it's not in the core API.![]()
I guess what I'm after is out of the plethora of options out there, which ones would be considered industry standard?
I don't believe one has emerged as the de facto standard yet. Your best be it probably to do a Google search and see what people are saying about the various options, pick 2 or 3 candidates, and see how they work for you.
Jeff Verdegan wrote:What do you mean "none that are native"?