Usage in JavaEE 7 application

[ebirn]

My primary use case for this ripple library is JavaEE server-side applications.

While this appears to be possible from the current state, some library changes could strongly improve its usability there, without impacting the use on other platforms such as Android.

2 things caught my eye: In both cases there exist javax.* apis, that could be used here, giving the advantage of the ability to use interchangeable implementations

• Websocket libs: javax.websocket.* (implementation example: Glassfish thyrus: https://tyrus.java.net)
• Json implementation: javax.json.* (ex. https://jsonp.java.net)

I consider the switching of the websocket implementation most important, as this is the only way to make use of application server resource pools (i.e. connection pooling, etc.). As far as the JSON implementation goes: when switching the websocket api one could also consider to move the json (de)serialization to a JAXB based one.

[sublimator]

I'm not really a Java specialist, can you explain what JAXB is?

[ebirn]

JAXB basically allows you to serialize/deserialize java objects directly to JSON or XML, using annotations on the classes and therefore reduces the boilerplate json creation code.

see here for an example: http://www.mkyong.com/java/jaxb-hello-world-example/

[sublimator]

Oh, that looks really neat :)

Does it use code generation or reflection?

[ebirn]

the latter, looking at the annotations at runtime, no code is generated.