Jonathan Hawkes wrote:
Yeah, I don't like it. What I love about the way the framework currently
works is that a component is still a stand-alone piece of software. It is
given reference to a ServiceManager and then it can put itself together
based on its needs. In my opinion, this way of doing things is more in line
with object-oriented thinking. The container should not have to know about
the component's internals. This is putting too much of a burden on the
container. A component should do what it does, and a container should do
what it does. When everything is doing what its supposed to do, then you
have a well-designed piece of software. Of course, defining the exact
responsibilities of the container and of the component is part of what we're
all about...
+1
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
