[
https://issues.apache.org/jira/browse/TAPESTRY-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568998#action_12568998
]
Howard M. Lewis Ship commented on TAPESTRY-2158:
------------------------------------------------
What happens there is that the JavaBeans framework interprets this as an
indexed property (it ignores the simple method and focuses on the second
version). Anyway, Tapestry can't really do anything with indexed properties,
so it ignores the property all together.
Your workaround is ${data.getPortfolioData().name}.
> Property does not work if two methods with different signatures
> ---------------------------------------------------------------
>
> 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
>
> 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]
