Congratulations on becoming a channel author Eric. ;-) I believe you
have the order correct for IChannel anyway. The only reason I can think
of to save the ChannelRuntimeData and PortalControlStructures values
across requests would be if they were going to have an effect on
isCacheValid. For example, returning true to skip rendering when values
have not changed. Not sure if this is ever applicable to your case though.
Susan
Eric Dalquist wrote:
Believe it or not the new portlet adapter channel for pluto 1.1 will
be the first channel I've ever written. To that end I want to make
sure I have some things figured out correctly.
The channel implements the IPortletAdapter, ICharacterChannel,
IPrivilegedChannel and ICacheable interfaces. From what I've seen the
following method call ordering is what I should expect for each type
of event targeting a channel:
init
setStaticData
render
setPortalControlStructures
setRuntimeData
generateKey
isCacheValid
renderCharacters
action //This doesn't exist yet but will be added to the
IPortletAdapter interface
setPortalControlStructures
setRuntimeData
doAction
event
setPortalControlStructures //This call doesn't happen before
receiveEvent currently but the change will be made in the framework to
ensure it does
receiveEvent
If those are correct, does it seem valid to clear out references to
the ChannelRuntimeData and PortalControlStructures at the end of the
renderCharacters, doAction and receiveEvent methods?
Thanks,
-Eric
--
It's no use trying to be clever--we are all clever here; just try to be kind--a
little kind.
-- F.J. Foakes Jackson
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
