[
https://issues.apache.org/jira/browse/TAPESTRY-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-755:
-----------------------------------
Fix Version/s: (was: 4.1.3)
4.1.4
> injection: Beware of where you declare the abstract method
> ----------------------------------------------------------
>
> Key: TAPESTRY-755
> URL: https://issues.apache.org/jira/browse/TAPESTRY-755
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0
> Environment: Tested on Tomcat 5.5.9 / JDK 1.5 / FC2
> Reporter: Henrik Vendelbo
> Priority: Minor
> Fix For: 4.1.4
>
> Attachments: InjectInheritance.html, InjectInheritance.java,
> InjectInheritance.page, SandboxPage.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
