[
https://issues.apache.org/jira/browse/TAPESTRY-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-2158:
-------------------------------------------
Priority: Minor (was: Major)
Summary: Tapestry will ignore a normal property if an indexed property
with the same name exists (was: Property does not work if two methods with
different signatures)
Workaround: don't do this :-) ... don't use indexed properties.
> Tapestry will ignore a normal property if an indexed property with the same
> name exists
> ---------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2158
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2158
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 5.0.11
> Environment: java version "1.6.0_03"
> Linux penfold 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
> GNU/Linux
> Tapestry 5.0.11-SNAPSHOT
> Reporter: Adriaan Joubert
> Priority: Minor
>
> If a class contains 2 methods
> public final PortfolioData getPortfolioData()
> public final PortfolioData getPortfolioData(int pId)
> the property access in the .tml file (an instance is retrieved through
> getData() in the page class)
> ${data.portfoliodata.name}
> fails with
> Could not convert 'data.portfoliodata.name' into a component parameter binding
> Removing the second method (public final PortfolioData getPortfolioData(int
> pId)) solves the problem.
--
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]