Currently, all Seam requests use "Get" and full-page refreshes with redirection. This causes the AS to leave portlet mode of operation and back to servlet....

Need to determine when this is desirable (if ever) and when it isn't (use-cases?) to determine possible solution(s).

For now the workaround is to use facelets and ICEfaces with Seam to create single page applications. Example of the seam-booking example is currently available at http://server.ice:8888/svn/ossrepo/projects/seam-booking-enhanced/trunk/seam-booking-enhanced

The logging in/authentication facility is still there (at creation of this jira), but authentication should probably involve checking to see that the user who has already logged into the container has proper authorization to run this application. Hopefully will get more input from users for this jira (and even the sample app).