https://issues.apache.org/jira/browse/TAP5-425
In our code we used some single letter properties. This used to work in
tapestry 5.0.15 or so.. but when we upgraded to 5.1-SNAPSHOT, tapestry
now fails at runtime with a very weird execption. Any clues to get this
fixed in tapestry would be appreciated.
Below is the exception, the getter we have in the page.java, and how
it's used in the page.tml.
## exception (runtime)
Could not convert 'K' into a component parameter binding: Node
<unexpected: [...@-1,0:0='<no text>',<-1>,0:-1], resync=null> (within
expression 'K') was type <invalid>, but was expected to be (one of)
IDENTIFIER, INVOKE, LIST, RANGEOP.
## .java
public boolean isK() {
return true; // if is of kicker type
}
## .tml
<t:if test="K">
...
</t:if>
The weird thing is that this keeps failing, even if I change the tml:
<t:if test="prop:K">
...
</t:if>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
