Field injection could actually avoid the circular dependency problem, it doesn't need to have all services ready for injection, constructor injection can't avoid it so only way is to use proxies there.
Denis Feb 16, 2012 v 10:50 PM, Thiago H. de Paula Figueiredo: > On Thu, 16 Feb 2012 18:20:29 -0200, Howard Lewis Ship <hls...@gmail.com> > wrote: > >> thing, it's just been a choice not to do so ... to have pure services >> (with an interface) have the full feature set (live reloading, late >> instantiation, proxies, decorators, advice) > > By the way, why don't proxies for interface-defined services have the > annotations copied from the implementation class methods to the corresponding > proxy methods? This makes people put annotations in interfaces instead of > service classes, and IMHO this breaks OOP principles very hard by putting > implementation details in an interface. Tapestry 5.2 supported that, but it > was lost in the transition to Plastic. I guess it wouldn't be hard to do that. > >> and have impure services >> (just an implementation) get minimal support (injection). > > Sounds good to me. :) > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
