I'll have to check into this; it should not be the case; if FeaturePage has an injection in XML, it should take effect, even when the abstract method is in MarketPage.
There *has* been some issues related to ambiguities in the names of properties; what is the name of the property to be injected? What you may be getting is a transient property (from the inherited abstract method) and a second read-only injected property, with similar names. On 11/16/05, hv @ Fashion Content <[EMAIL PROTECTED]> wrote: > Hi all, > > I finally tracked down the issue I have been having with injection > > Take the following class hierachy: BasePage -> MarketPage -> FeaturePage > > If you inject into FeaturePage using an <inject> tag in the page file, but > the abstract method is declared in MarketPage, the enhanced version of > FeaturePage will _not_ have an implementation of the accessor method. > > If you try to declare the abstract method in FeaturePage as well, it will > _not_ have an implementation of the accessor method. > > If you instead do an @InjectObject in MarketPage(and remember to remove the > inject tag), the enhanced FeaturePage class will have an implementation of > the accessor method. > > I other words the current functionality requires that you inject into the > class that first declares the abstract method, and not a sub class. > > Hope this will save someone a couple of days headache. > > Cheers, > > Henrik > > > > > --------------------------------------------------------------------- > 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]
