[seam-dev] Re: Seam/RESTEasy integration

[Dan Allen]

>
>> 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).
>>
>>
>
> Why can't POST be used?  Sys admins and caches don't understand an
> action-oriented world, but they do know the difference between GET and POST.


I don't think we are disagreeing. You have to use GET + action that changes
state for something like an activation URL in an e-mail. In this case, you
don't have control over the client to make it a POST. But like I said, this
is really up to the developer. The point is, JSF 2.0 starts to make the
distinction possible...and correct by default. In JSF 1.2, it was POST or
hit the road Jack.

-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/fbce53f7/attachment.html