> I don't know how extensible Jersey/Restlet are, but I think > Wink is simple to extend and customize if need be.
Sounds like we need a section under the base user guide that outlines how to do this. I agree that it's possible and easy todo, but people are never going to find out about it if they have to dig for it. -N Nicholas Gallardo WebSphere - REST & WebServices Development [email protected] Phone: 512-286-6258 Building: 903 / 5G-016 Bryant Luk <bryant....@gmail .com> To [email protected] 08/12/2009 01:43 cc PM Subject Re: JAX-RS Stack comparison(s) Please respond to wink-...@incubato r.apache.org I would suggest looking at: http://incubator.apache.org/wink/docs/Apache_Wink_User_Guide.pdf for the above and beyond JAX-RS features. The source code base is also of course Apache licensed compared to Jersey/Restlet. Compared to CXF, Wink is specifically focused on REST applications (which can be a good or bad thing depending on what you want). I don't know how extensible Jersey/Restlet are, but I think Wink is simple to extend and customize if need be. On Wed, Aug 12, 2009 at 1:22 PM, Davanum Srinivas<[email protected]> wrote: > Team, > > Here's some feedback on twitter....so WDYT? Why/How are we better than the > competition? > > @mraible - tried Apache Wink? - http://incubator.apache.org/wink/ > @dims Nope, but a 0.1 release in incubation doesn't seem like something I > should recommend to clients. ;-) > @mraible - i understand. but fyi, they did pass the JAX-RS TCK - > http://bit.ly/SjRTx > @dims So why is it better than Jersey, Restlet or CXF? > > thanks, > dims > -- - Bryant Luk
