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 O
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
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.
--
Best
And obviously, I meant "every service that it somehow depends on"
instead of the other thing which is not true.
Op 22-11-2010 0:34, Tom van Dijk schreef:
Well, no, you will see that a lot of services depend on each other, so
in order to create an object that just happens to depend on stuff like
Well, no, you will see that a lot of services depend on each other, so
in order to create an object that just happens to depend on stuff like
object providers, many other services need to be created. This is not an
inefficiency in Tapestry (The services are first only "virtual" before
they are
