[TAP5-921] Properties defined in an Interface are not exposed by PropertyAccess for abstract classes that do not directly implement the methods

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1.0.5
• Fix Version/s: 5.2.2
• Component/s: tapestry-ioc
• Assignee: Josh Canfield
• Reporter: Peter Rietzler
• Created: 06/Nov/09 08:37
• Updated: 17/Oct/10 20:34
• Resolved: 17/Oct/10 05:42

Description

Here is a simple example:

public interface HasName {
String getName();
}

public abstract class AbstractBean implements HasName {
}

public class TestPage {

@Property
private AbstractBean bean;

public void onActivate() {
bean = new AbstractBean() {
public void setName(String name) {
}
};
}
}

TestPage.tml
...
<h1>${bean.name}</h1>
...

Error message is:

Exception assembling root component of page manager/tools/TestPage: Could not convert 'bean.name' into a component parameter binding: Class smarter.ecommerce.smeco.manager.pages.tools.AbstractBean does not contain a property named 'name' (within property expression 'bean.name'). Available properties: class, componentResources.

Everything works fine if I change the bean class to:

public abstract class AbstractBean implements HasName {
public abstract String getName();
}