blog.stringtree.org » Blog Archive » New release of Stringtree, now with easy JSON

New release of Stringtree, now with easy JSON

It’s been a while since I put out an updated version of Stringtree. There have been a steady stream of changes and additions, so I reckon it’s time for a new one. Say hello to Stringtree 2.0.5.

Changes in this version:

added templater test for calling a pipe on an object before multiplying
added initial mock implementation of JDBC classes
reintroduced some Tract Fetcher tests. Not all working yet, though.
added quot and apos to XMLEscaper
migrate juicer & tests
migrate workflow and tests
reformat Juicer code to new standard
add juicer tests into main test sequence
add workflow tests into main test sequence
go through all code and check formatting
write JSON validator
add MapResultRowListener to collect name/value pairs from database results
(spec) support use of @ and ! with no names as resource and filesystem includes
(JSON) write documentation and examples
(JSON) notify JSON.org
modify build script to generate separate stringtree-json jar

One of the most significant changes is that JSON now gets its own sourceforge binary release and even its own web page. Stringtree JSON has been a surprising success, so I thought I’d make it easier for people to understand and use it without the rest of the Stringtree library.

Posted by Stringtree in JSON, Projects

This entry was posted on Monday, March 26th, 2007 at 11:11 am and is filed under JSON, Projects. You can follow any responses to this entry through the comments RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.

7 Responses to “New release of Stringtree, now with easy JSON”

Kaveman’s Daily Feed of Informative Blogs » New release of Stringtree, now with easy JSON says:

[...] Original post by Stringtree [...]

March 26th, 2007 at 11:56 am

Seth says:

Stringtree appears to be the best of breed for Java JSON libraries. Which classes are threadsafe? Thank you!

March 27th, 2007 at 2:21 pm

Stringtree says:

Seth, thanks for the nice words, and an interesting question.

None of the Stringtree JSON classes are explicitly threadsafe. They are Object-Oriented in that each object manages its own state during a sequence of internal method calls.

I recommend that each thread, or each method call which might be used in a multithreaded environment construct a new JSONReader or JSONWriter object. In general this should not be a major issue, though, as they are all deliberately very light to construct. I generally recommend treating a JSONReader or JSONWriter as you would a StringBuffer or other state-managing object.

However, adding explicitly threadsafe versions of the “JSON trilogy” classes is an interesting idea. I’ll think about it and see if it can be done in an effective way.

March 28th, 2007 at 8:40 am

JÃ¶rn Zaefferer says:

I’ve already enjoyed using Stringtree JSON a lot. A few issues I found, mostly related to my requirment of running on JRE 14.:
- I had to remove the check for Iterable in JSONWriter and compile the JAR file for 1.4 to get it working
- removing the support for iterable disables support for any collection classes, eg. I have to call ArrayList.toArray(), otherwise only the arraylist object is serialized

I really wish I could use Java 5 myself, but currently it looks like I’ve still got to wait for a few years. It would be great if you could make Stringtree JSON compatible with 1.4 out-of-the-box. Considering the very little amount of dependency on Java 5 it should be quite easy to achieve.

Regards
JÃ¶rn

April 17th, 2007 at 1:08 pm

Stringtree says:

Thanks for the comment. I have been intending for a while to fix this and make Stringtree JSON 1.4 compatible again. The “Iterable” slipped in because I typically develop on Java 5, and even though I tell Eclipse to use Java 1.4 mode when developing Stringtree, it’s not smart enough to warn against the use of Java 5 APIs.

Expect a 1.4 compatible version soon!

April 17th, 2007 at 2:38 pm

JÃ¶rn Zaefferer says:

Thanks, thats great news.

At least you can tell Eclipse to use a specific JRE for a project, so you can just install a 1.4 JRE and set your project to use that.

April 17th, 2007 at 3:31 pm

Stringtree says:

I might just try that, although it would mean installing an extra JRE on all the various machines I develop on.

As a side note, there is now a shiny new release at Sourceforge. Please feel free to let me know of any other suggestions!

April 17th, 2007 at 3:47 pm