I'm sure Tapestry could do some byte code magic via plastic such that any @Inject fields accessed in the constructor were swapped out for getters with nice error messages. Sounds very messy / intrusive to me and I don't think it should be implemented. On 7 Apr 2014 13:54, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> wrote:
> On Sun, 06 Apr 2014 16:26:47 -0300, John <j...@quivinco.com> wrote: > > problem solved, the Logger was of course not yet injected! Duh. I wish >> the IoC stack dump were more helpful. >> > > I'm not sure how (a better error message) that could be done. How could > Tapestry-IoC differentiate an exception caused by field injection not done > yet from other exceptions? Even if it's just about NPEs, I cannot see how > that could be done. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
