[seam-dev] Re: Seam/RESTEasy integration

[Dan Allen]

Thanks for the response Bill. Let's line that up with what we have today.


> * Unique URIs to each "page"


We are going to call these "pretty" or "friendly" URLs and it is slated for
JSF 2.1. We intentionally want to avoid the word REST here.


>
> * don't overload the meaning of HTTP methods.  i.e. don't change state of
> server with a GET


JSF 2.0 will have bookmarkable URLs, which are used, for example, to
retrieve a record by ID. In JSF 2.1 we intend to add page actions, which may
change the state of the server with a GET, but those are discretionary cases
to adapt to an action-oriented world (sometimes, it just has to be done).


>
> * No sessions, stateless


JSF 2.0 if they get their act together.


> Or maybe people just want nice URI templating and JAX-RS injection
> annotations.  I don't know. Which isn't persay, "REST", but still nice to
> have.


This was my favorite idea of what was discussed in Tuscany. I'm going to
credit Christian with sparking this idea. Correct me if I'm wrong.

-Dan

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20090304/135d4188/attachment.html