I already am watching for method calls on the Render and Action
Request - but my problem is that what if they call a Sakai API
*before* they even touch the Request objects. I need to be assured
that the thread is properly provisioned *before* the first line of
the Render or Action executes.
/Chuck
On Mar 4, 2007, at 3:33 PM, Eric Dalquist wrote:
Note what uP3 does. We have a custom impl for RenderRequest and
ActionRequest that we provide to Pluto. The current use is this
request watches for a portlet trying to access the USER_INFO Map
and we actually do a DAO call in the *Request object. We also
provide a custom PortletPreferences impl via these objects since we
have a fairly complex prefs hierarchy that requires a custom
implementation.
Are there still things that you couldn't do with custom request
objects that you need a listener for?
Not saying it isn't a good idea, sounds like a neat hook, just not
sure it actually needed or more useful than just having custom
request objects.
-Eric
