Hallo Sebastian,
Well, you will always need the ObjectProvider, and it in turn will
always need a number of services, either virtual or realized. Maybe
there is a way to draw dependency diagrams so you can really see what is
going on (but as far as I know, this information isn't available from
the IoC right now, it's on my list of things to do and be excited about)
But again, these services aren't actually instantiated yet; at least not
until they are needed.
Op 22-11-2010 22:20, Sebastian Hennebrueder schreef:
Hi Tom,
I wasn't surprised by the number of services to be prepared either as proxy or
to be created. I just don't see a reason why the object provider which I add as
last provider is called for framework internal services. There is just no need
to call it at all for those services.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
