This is explained, more or less, on the injection page http://tapestry.apache.org/ioc-injection.html
When processing an injection, Tapestry starts by seeing if there's an unambiguous service that can be injected. Following that it falls into the MasterObjectProvider service, and its contributed ObjectProvider instances, in particular ServiceOverrides. At the end of that chain, it does another check for the service and reports an error if none can be found or if the match in ambiguous. On Mon, Nov 22, 2010 at 4:40 PM, Tom van Dijk <t...@tvandijk.nl> wrote: > 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 > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
