Well, it occurs to me that both JAX-RS and Jersey dosen't define
client-side API's (however, other JAX-RS based frameworks do, like Restlet
and RestEasy, if I'm not mistaken....)
So to build a full Web app you have to use Jersey *and* something else...
(i'm reading your blog post by pieces, i must say...)
On Jan 27, 2009 3:45pm, James Strachan <james.strachan_at_gmail.com> wrote:
> I've been pondering this for a little while; is JAX-RS the kinda long
>
> term replacement for all the zillions of web frameworks out there?
>
>
>
> I tend to think, yes it mostly is for most requirements - and we're
>
> nearly there, just a few things to fix up and improve. I've just
>
> blogged (a rather long post for me) about it, brain dumping my
>
> thoughts
>
>
http://macstrac.blogspot.com/2009/01/jax-rs-as-one-web-framework-to-rule.html
>
>
>
> it could well feed the trolls but it'd be interesting to hear if
>
> others have been having similar thoughts (or maybe I'm just smoking
>
> crack :). From seeing folks hit similar issues to me in the implicit
>
> views / static files /JSP mappings areas - it looks like at least a
>
> few folks are trying to do similar things.
>
>
>
> Thoughts?
>
>
>
> --
>
> James
>
> -------
>
> http://macstrac.blogspot.com/
>
>
>
> Open Source Integration
>
> http://fusesource.com/
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
>