I suppose I am looking at iPojo from the perspective of Guice and
PicoContainer. The first tries to replace all object construction, while
the second tries to do that and on top of it manage the subsequent
lifecycle of objects. Still both of them operate within the usual OO
paradigm. They just try to enrich the Java language with facilities that
make it easier to do OOP.
iPojo seems to come from some "component" world which I have not grasped
well yet. Seems component != object and one should not strive to make a
component out of every object :)
Hope I have not made this thread too philosophical and tedious to read :)
Cheers,
Todor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
