Resteasy Project: JAX-RS Restful Web Services implementation
Posted by billburke on February 25, 2008
I’m pleased to announce the first beta release of the JBoss Resteasy JAX-RS implementation!
After about 4 months of on and off development, I finally have a working version of the new JSR-311, JAX-RS specification. For those of you who don’t know, JSR-311 is a RESTFul Web Services implementation for Java and is slated to be included within Java EE 6. The spec is still a bit of a moving target, but its still pretty useful. Let me know what you think!
Features:
- JAX-RS implementation (almost full, still have a few minor things here and there)
- Portable to any app-server/Tomcat that runs on JDK 5 or higher
- EJB 3.0 and Spring integration
- Client framework to make writing HTTP clients easy (JAX-RS only define server bindings)
Where can I find out more?
All information, including where to download it, is available on our Resteasy WIKI.
blpsilva said
Hi Bill, i didn’t know you guys at JBoss were developing an implementation of this JSR.
This is really great news. I took a look on the Jersey project and found it very interesting. It’ll be nice to see this implementation of yours, given that I’m a longtime JBoss user.
alrubinger said
Congratulations on the milestone.
S,
ALR
Dan Diephouse said
So I’ll bite: why would I ever use this over Jersey? I believe Jersey has all those things you list as well.
Apache CXF also has an implementation in progress. Once again I’m not sure of the value, but at least there you can make the case that because its unified with the JAX-WS implementation you can leverage some benefits (common deployment, common config, etc). Personally I would’ve rather seen CXF embed the RI though.
billburke said
@Dan:
Why over Jersey?
1) The specification is simple enough to implement. I want our own so that we can innovate on our own without having to get permission from jersey or the specification. There’s already one feature (pojo mappings) that I want to try out and the spec lead does not want in the specification.
2) I don’t want to be constrained by any part of the jersey architecture when I integrate it with JBoss and our EJB container.
3) I’ve already “innovated” (if you can call it an innovation) on the client framework. AFAIK, the jersey does not have this feature
4) If Apache CXF can implement JAX-RS why can’t JBoss?
5) I could give two shits about Apache CXF
I can leverage JBoss’s common deployment and config when I create tighter integration.
6) I have borrowed and will borrow extensively from the Jersey testsuite. This is, IMO, where the real value of Jersey is. The specification is incredibly easy to implement on its own.
alesj said
Tell us more about the Spring integration.
alesj said
Or better, how can we use MC and ditch Spring.
Ryan J. McDonough said
Just FYI, the name should be written as RESTEasy as opposed to Resteasy or RESTeasy
Thanks for finishing off the coding effort too 
Ryan-
DamnHandy : » Announcing JBoss RESTEasy Beta1 said
[...] case you didn’t see Bill’s post on the subject, I wanted to let folks know that RESTEasy entered it’s first beta release as JBoss RESTEasy [...]
Dan Diephouse said
I’ll add that Jersey already has a bunch of different connectors: Grizzly, a small embedded HTTP Server, Servlets, JAX-WS and one I wrote for Mule. Its pretty damn easy to integrate and its been proven to integrate well on a bunch of different platforms.
Serge Pagop said
Great news Bill, I will try that.