Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
5.1.0.0
-
None
Description
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 getter we have in the page, the tml of the page, and below that we have the exception throws by tapestry at runtime.
-
- .java
public boolean isK() {
return true; // if is of kicker type
}
- .java
-
- .tml
<t:if test="K">
...
</t:if>
- .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.
- exception (runtime)
The weird thing is that this keeps failing, even if I change the tml:
<t:if test="prop:K">
...
</t:if>
Attachments
Issue Links
- is duplicated by
-
TAP5-426 one letter property name breaks page or component classes
- Closed