Hi, Have you considered the javax.json API? There are some parts that may not be able to be directly translated but from memory it should mostly work. The "advantage" is that it is a standard that is starting to gain traction and will likely be present in lots more APIs as more of the EE stack adopts it. The "disadvantage" is that the api is a bit more primitive and it evolves slowly. It could probably be done with just @JsOverlay methods and a few adapter classes. Another disadvantage is that it is an immutable/read-only API.
As for json writing - We tend to use @JsType annotated classes and have yet to come up with a use case where we would need to drop down to JsPropertyMap. -- Cheers, Peter Donald -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc6_RvyT7RaQ8r87bXcexVvGB%2BmtFCiATZrY-aNcB%2BYKEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
