transient state and portlets

[Mike Perham <Mi...@webifysolutions.com>]

http://jakarta.apache.org/tapestry/tapestry-portlet/coding-issues.html#L
oss+of+Transient+State

Portlets have one major different in their programming model versus
servlets: data in the rewind phase is not available during the render
phase.  The link above recommends making your page properties
session-persistent so they are available to the render phase.
Personally I think this will lead to a mess of a session or require the
developer to clean up the session by hand.  I was wondering if anyone
else had any thoughts on infrastructure that Tapestry could provide that
could lead to a cleaner portlet programming model.

http://opensource2.atlassian.com/confluence/spring/display/WEBFLOW/Portl
et+Integration

Spring Webflow's Portlet integration has a notion of a ViewDescriptor;
the action code puts variables in the descriptor which is made available
to the render phase via the session.  I would assume that this
descriptor is cleared from the session when the request is complete -
which is a much tidier solution.  Obviously this is nothing that the
application developer couldn't provide themselves but having it
integrated into Tapestry would make it that much simpler and cleaner for
the portlet developer.  Any other thoughts?

mike

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org