[picocontainer-dev] annotations and comments on Pico2

>My position on annotations is somehow mixed - I think they are usefull
in certain situations ( like internal wiring of xwork-2 , which is
basically guice ) but they also introduce unflexibility when you need
external configuration

Konstantin, not sure what you mean by "unflexibility". And do you mean
you rather would not have any annotations in the container?

I looked at ComponentCharacteristics but I'm not sure to understand at
what level it works. There is a single instance (rc) at the container
level, so does it mean that all component adapters of one container will
have the same characteristics? If that's the case, I'm not very keen of
having a state at the container level for managing the properties of all
components. This whole concept of ComponentCharacteristics introduces
IMO unnecessary complexity in the code. I think pico needs a way to take
a list of characteristics and generate a list of component adapters and
this by container (for default) but also per CA and by many methods
(annotations or something else). 

Also it would be nice (at least I would need that...) if there was a
"post-process" method in the container and CA that would allow to post
process stuff on existing instances:
- process setters on an existing instances;
- process annotations on existing instances.

Erik Putrycz, Ph.D - Research Associate / [email protected] /
(613) 990 0681
Institute for Information Technology - Software Engineering Group
National Research Council, Canada - Building M-50, 1200 Montreal Road
Ottawa, Ontario, CANADA K1A 0R6

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email