> From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > Leo Sutic wrote: > >Thoughts? > > > > Maybe I'm just too old fashion - but this is like sleeping with the > enemy. If I - as component writer declare something as > private - then what I'm saying is that its off limits to others > including the container.
I thought that too. On the other hand, you *have* declared it as a field where the container should set the value. So it's not like you're not getting what you asked for. > From: Jonathan Hawkes > > The container should not have to know about the component's > internals. In a way that is not possible - the container has to know some things about a component. Its dependencies, for one. What I am trying to achieve is to use attributes to make the container carry out specific actions - i.e. set this field to that, and so on. So, the container will not know anything about the internals that you haven't declared with attributes. This isn't that different from declaring it in an XML file. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
