Another doubt I've with pico is its component dependencies resolving by type matching only strategy. I think this might not be sufficient in some scenario.
--- 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) > 2) Ability to resolve component dependencies and create components with > dependencies fulfilled > 3) Ability to re-wire component dependencies separate from construction > -> needed to re-wire components after serialization / deserialization > > Picocontainer can not and will not (as far as I can discern from the > mailing list) support requirement 3, so I suggest we remove > Picocontainer and restore the previous IoC code for now, while we > examine other alternatives, such as Spring. > > Jason > -- > Jason Carreira > Technical Architect, Notiva Corp. > phone: 585.240.2793 > fax: 585.272.8118 > email: [EMAIL PROTECTED] > --- > Notiva - optimizing trade relationships (tm) > > > > ------------------------------------------------------- > 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 __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ------------------------------------------------------- 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
