[XSTR-687] StAXONDriver (JSON)

Details

Type: New Feature
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: IO
Labels:
None

Description

I posted this on the user-list before and was asked to create a JIRA issue...

I am currently working on StAXON - JSON via StAX. In principle, this thing is similar to the well-known Jettison, however, StAXON provides a more complete StAX implementation and tries to avoid some of the issues people have with Jettison. See http://beckchr.github.com/staxon/ for more.

As a proof of concept, I wrote a simple XStream driver for StAXON, which seems to work pretty well and may serve as an alternative to the existing JSON drivers available for XStream. I'm attaching the code with simple tests, so if anyone is interested?

The code is contributed, so feel free to modify or distribute the code with XStream under a BSD-like license.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

StAXONDriver.java

15/May/12 6:56 PM

7 kB

Jörg Schaible
StAXONDriver.java

07/Jan/12 11:41 AM

7 kB

Christoph Beck
StAXONDriverTest.java

15/May/12 6:57 PM

15 kB

Jörg Schaible
StAXONDriverTest.java

07/Jan/12 11:41 AM

5 kB

Christoph Beck

Activity

Hide

Permalink

Jörg Schaible added a comment - 15/May/12 6:55 PM

Hi Christoph,

this looks very promising. To get a better overview I have ported XStream's tests for the Jettison driver to your StAXON driver. Following differences/problems catch my eye:

numeric (and boolean ?) types are written as JSON strings (you get the type in the overwritten startElement of the writer)
forward slashes are not escaped (www.json.org seems to imply such a behavior)
empty arrays/lists are not written as empty JSON arrays (Jettison fails here also)
invalid JSON can be generated for Externalizable types (Jettison fails here also); it might be possible to treat Externalizables as multi-type, but then we get:
similar problem applies for any List with different type of elements (Jettison fails here also), but the question ist, how to represent this in JSON at all:
```
<list>
  <string>foo</string>
  <int>42</int>
  <string>bar</string>
</list>
```

However, thanks so far
Jörg

Show

Jörg Schaible added a comment - 15/May/12 6:55 PM Hi Christoph, this looks very promising. To get a better overview I have ported XStream's tests for the Jettison driver to your StAXON driver. Following differences/problems catch my eye: numeric (and boolean ?) types are written as JSON strings (you get the type in the overwritten startElement of the writer) forward slashes are not escaped (www.json.org seems to imply such a behavior) empty arrays/lists are not written as empty JSON arrays (Jettison fails here also) invalid JSON can be generated for Externalizable types (Jettison fails here also); it might be possible to treat Externalizables as multi-type, but then we get: similar problem applies for any List with different type of elements (Jettison fails here also), but the question ist, how to represent this in JSON at all: <list> <string> foo </string> <int> 42 </int> <string> bar </string> </list> However, thanks so far Jörg

People

Assignee:

Jörg Schaible

Reporter:

Christoph Beck

Votes:

0 Vote for this issue

Watchers:

0 Start watching this issue

Dates

Created:

07/Jan/12 11:41 AM

Updated:

15/May/12 6:57 PM