Nope; I missed something. During the "rennovation" of Vlib, I saw that I could collapse a confusing inheritance hierarchy down to a single base class, by replacing behavior-with-inheritance with behavior-by-configuration (of @Meta data).
On 11/18/05, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > I'm taking the Virtual Library examples in the source tree as a > reference best practices for a prototype I'm producing and looking at > Login page and VlibPage i notice that both have the ValidationDelegate > beans injected even if Login page extends from VlibPage, so i guessed > Login shouldn't need to have: > @Bean(VirtualLibraryDelegate.class) > public abstract IValidationDelegate getValidationDelegate(); > > Did i miss something? > -- > Massimo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
