I'm actually not sure; I suppose we could switch it around to use the passed-in ObjectLocator and run the tests to see what happens ... I suspect the only difference would occur if a field had the @Local annotation on it (though I'm not sure if it would be ignored, or simply give odd results).
Injection gets tricky with services and configuration objects that themselves help implement injection (or, more specifically, object resolution for dependency injection). On Tue, Jul 19, 2011 at 6:58 AM, Tom van Dijk <[email protected]> wrote: > Hi! > > The two injection providers DefaultInjectionProvider and > ServiceInjectionProvider both use services (ObjectLocator and > MasterObjectProvider) provided at construction time rather than the object > locator provided as a parameter to the provideInjection call. > > Is this correct behavior? > > Tom. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
