Yes, I believe you missed something here. Read my last post carefully again. We're talking about two containers here (or even three, if you consider sessions too).By combining PicoContainers in hierarchies. Very much like ClassLoader hierarchies. Have aq look at what Joe has done in nano for servlets/webwork.
The app scoped component would live in an app scoped container. Then onIe if you have an application scoped component, which gets a request scoped component set on it - it's already constructed, so uh - eh? :)
a new request you create a new (short-lived) container for that request
only (using the parent container as parent). Makes sense?
Uhm - not really. Isn't the whole point of an app scoped container that only one is created, and it lasts for the scope of the whole application? If you're creating a new one each request, surely it's just a request scoped container then? :)
Or did I miss something here?
appContainer contains sessionContainer contains requestContainer.
They're all instances of PicoContainer, but organised in a hierarchy (like ClassLoaders) and with different life length.
Am I not making myself clear here?
Aslak
M
Aslak
Mike
On 25/6/03 8:12 AM, "Pat Lightbody" ([EMAIL PROTECTED]) penned the words:
I'll be checking out pico this weekend. Joe, I expect you to be helping out :)
----- Original Message ----- From: "Joe Walnes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, June 24, 2003 5:36 AM Subject: [OS-webwork] Re: [picocontainer-dev] Picocontainer/Nanocontainer
-------------------------------------------------------IMO we should migrate Xwork.Of course :).
FWIW, Nano already supports WebWork 1. Should be easy to port to XWork/WW2. It is also very useful outside the scope of web projects.
-joe (author of original IoC stuff in WW2 - if you care) ;)
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
_______________________________________________ picocontainer-dev mailing list [EMAIL PROTECTED] http://lists.codehaus.org/mailman/listinfo/picocontainer-dev
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
