RE: [OS-webwork] Data spanning several actions and req-resp trips

[Patrick Lightbody]

IoC (and interceptors for that matter) are just one way to skin a cat. You could of course use ActionContext.getContext().getSession() just the same.   What do you mean “manage the IoC container”?   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergio Infante Sent: Friday, February 20, 2004 11:42 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Data spanning several actions and req-resp trips   If you have a group of actions, lets call this a function, that act on data that needs to be persisted during the length of a session, the most obvious way for me to handle this behavior is by creating a component and corresponding enabler interface for each function (group of actions) and having each action in the group implement the enabler. However, in a complex application, or a group of applications running in the same context, the number of such interfaces could get out of hand. Are there alternative ways present in Webwork to handle such need? Action flow?   Are interceptors an alternative?   As a separate issue, can interceptors manage the IoC container?   Thanks for input.