Author: kmenard
Date: Sun Mar 8 05:05:49 2009
New Revision: 751367
URL: http://svn.apache.org/viewvc?rev=751367&view=rev
Log:
Note that passing a List of Strings as a model to Select component will build
up a model around that list.
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Select.xdoc
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Select.xdoc
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Select.xdoc?rev=751367&r1=751366&r2=751367&view=diff
==============================================================================
---
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Select.xdoc
(original)
+++
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Select.xdoc
Sun Mar 8 05:05:49 2009
@@ -26,7 +26,8 @@
</html>]]></source>
<p>
- When the model parameter is a string, it is split apart at
the commas.
+ When the model parameter is a string, it is split apart at
the commas. When the model parameter is
+ a List of Strings, each element is considered a selection
option.
</p>
<p>
@@ -36,9 +37,8 @@
<p>
Here the label displayed to the user is the same as the
value used to update the property, but that
- doesn't
- have to be the case. By specifying a value and a label, we
can control the server side value without
- changing how the UI appears to the user:
+ doesn't have to be the case. By specifying a value and a
label, we can control the server side value
+ without changing how the UI appears to the user:
</p>
<source>
