JAX-RS 2.0 is around the corner. We’re ironing things out in the JSR group and alpha implementations should be out soon along with the public draft. I talked to O’Reilly and the sales of my Restul Java book were good enough to justify a revision. So…
What do you want in Restful Java 2.0?
The obvious things are new spec features, specifically new chapters on:
- Client API
- Filters and Interceptors
- Asynchronous HTTP
There’s a few other minor features that will be sprinkled about in existing chapters of the book. We’ll also need to update the Java EE integration section as when the book was written, it hadn’t really be finalized yet.
For the filters and interceptors chapter, I was thinking about walking through (with code examples) the use cases that were the inspiration for these features in the spec.
For the asynchronous HTTP chapter, I was thinking of using/implementing a slimmed down simple version of the HornetQ REST interface. That way I can throw in bits about Atom as well as some useful restful patterns.
For security, I was thinking of talking a bit more about Resteasy’s S/MIME and DKIM support and how they fit into the security picture. We could also talk about OAuth too.
What else? Please comment.
Bill the Plumber 
Aug 29, 2012 @ 23:47:25
Hello Bill,
It would be great if you add something related to HATEOAS. I checked the JAX-RS 2 draft recently and it is not there, there’s no mention to linking.
Perhaps also explore some enterprise API, but I don’t know if it’s still in the book scope.
Aug 30, 2012 @ 19:07:14
howto update existing Java 6 EE containers to JAX-RS 2.0
Aug 31, 2012 @ 03:02:40
1. Client API, including standalone clients.
2. MessageBodyReader and MessageBodyWriter for complex object graphs and Collections.
3. Security, including standalone clients.
Distributed Weekly 170 — Scott Banwart's Blog
Aug 31, 2012 @ 10:26:45
Sep 27, 2012 @ 18:47:33
I would like to see building a jax-rs from the beginning using a pojo data model.
Then I would like to see a(web service) factory annotation pattern used for the purpose of a jms spring integration or net beans or oracle aq.
Thank you
Bill S
Oct 22, 2012 @ 11:00:42
Hi Bill,
Having the first edition, i would really enjoy having more details on :
– Asynchronous HTTP (and maybe how to integrate it with asynchronous EJBs)
– Concurency and Conditionnal POST/PUT, but on the client side …even if it is not really a JAX-RS matter. How to manage a stale exception ? What are the strategies that are applied in these cases ?
– OAuth + the client side
– Optimisation issues, scale with large graph objects (Lists of lists of lists) … ?
Thank you!
Vincent.
Oct 22, 2012 @ 13:35:12
The problem with OAuth on the client side, is that the actual authentication mechanism is undefined. So, you’d pretty much have to implement client support for each authorization server.
Oct 30, 2012 @ 05:59:21
Nervertheless it still would be great to see some example implementation of it in part two of the book. In PAAS Cloud solutions you see the support of OAUTH(2) popping up more and more. With mobile clients talking to a Rest layer in the cloud it would be a nice niche I think. (Although non-cloud solutions are of interest as well ;-))
Oct 22, 2012 @ 11:02:00
Hi Bill,
Having the first edition, i would really enjoy having more details on :
– Asynchronous HTTP (and maybe how to integrate it with asynchronous EJBs)
– Concurency and Conditionnal POST/PUT, but on the client side …even if it is not really a JAX-RS matter. How to manage a stale exception ? What are the strategies that are applied in these cases ?
– OAuth + the client side
– Optimisation issues, scale with large graph objects (Lists of lists of lists) … ?
Thank you!
Vincent.