I've only looked at Pico briefly from Paul Hammant, and it does look good. I
kinda like the enabler interfaces personally though, they're nice and neat.
Neat - but pointless.
How does Pico handle things with different scopes I wonder?
Same way as XWork. Each container can have a parent container.
Ie if you have an application scoped component, which gets a request scoped
component set on it - it's already constructed, so uh - eh? :)
You can't do this - intentionally. It's an invalid contract if you
specify that a component depends on another component that has a shorter
lifespan. This typically illustrates a design smell - it makes little
sense for one component to call another component that no longer exists.
-------------------------------------------------------
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
