You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by hl...@apache.org on 2010/03/13 03:47:19 UTC
svn commit: r922470 -
/tapestry/tapestry5/trunk/src/site/apt/guide/propexp.apt
Author: hlship
Date: Sat Mar 13 02:47:19 2010
New Revision: 922470
URL: http://svn.apache.org/viewvc?rev=922470&view=rev
Log:
TAP5-632: Update some documentation
Modified:
tapestry/tapestry5/trunk/src/site/apt/guide/propexp.apt
Modified: tapestry/tapestry5/trunk/src/site/apt/guide/propexp.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/src/site/apt/guide/propexp.apt?rev=922470&r1=922469&r2=922470&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/src/site/apt/guide/propexp.apt (original)
+++ tapestry/tapestry5/trunk/src/site/apt/guide/propexp.apt Sat Mar 13 02:47:19 2010
@@ -34,11 +34,15 @@ Property Expressions
Being able to invoke methods was originally added so that it was possible to access methods such as
java.util.Map.size() (which is not named like a property getter method). In Tapestry 5.1, property expressions
were extended so that parameters could be passed into methods.
-
+
Parameters to methods are, themselves, property expressions. This means that you can write a property expression
that reads a property and passes it as a parameter to a method, and then access a property of the object returns
from the method.
+ Starting in release 5.2, property expressions may also reference public fields of data objects as if they were
+ true properties. Tapestry will simply read and update the field, rather than invoking getter and setter methods.
+
+
Compilation
Property expressions are compiled to Java classes at runtime; there is no runtime reflection (unlike