> -----Original Message----- > From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] > Sent: Friday, July 11, 2003 10:33 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Xwork IoC requirements > > > > --- Jason Carreira <[EMAIL PROTECTED]> wrote: > > I'm starting a list of requirements for an IoC > > container in Xwork. > > Here's what I've got so far: > > > > 1) Ability to have nested component scopes > > (Application -> HTTP Session > > -> HTTP Request -> Action Invocation) > > AFAIK, xwork shoid be web-agnostik, or what's puprose > of splitting ww2 / xwork?
Yes, they should. But that doesn't mean nested component scopes isn't a requirement, as the main user of Xwork right now is WebWork, and it needs nested scopes. The scopes I listed were just an example. > > And I have another concern - lifecycle of session > scope. There should be possibility of catching sesion > invalidtion event properly, and not like this is done in > tomcat ( or maybe other servlet containers ) > > Currently session listener will be called after > session > invalidation, so it's impossible to look into it. > > And implementing interfaces from javax.servlet by > objects stored there is not so cool... > This is a valid concern. I think we'll have to figure out these issues as we go. Jason ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
