Lance,
Tapestry does not do this at present.
(Sounds a bit like the struts mechanisms.:)
Rather than using reflection to examine the name of the form field
and find an associated property name, tapestry relies on bindings to
do the job. Which is nice, really, because you don't /have/ to
have a property on your page called e-mail. You could have a user
object as a property, and then bind the text field to user.email.
Since tapestry is not looking for properties based on parameter names,
you don't have the worries of malicious users tinkering with parameter
names to see what properties are available/settable. ;)
Robert
Lance Arlaus wrote:
> I'm just getting started with Tapestry 4.0 and had a quick question:
>
> Is it possible to omit the value attribute on a component and still have
> Tapestry intelligently bind to a corresponding property on my page class.
>
> In other words, given the following, will Tapestry successfully bind?
>
>
>
> Page:
>
> .
>
> <input jwcid='[EMAIL PROTECTED]'/>
>
> .
>
>
>
> Page Class
>
> public abstract class MyPage extends BasePage {
>
> public abstract String getEmail();
>
> .
>
> }
>
>
>
> I'd give it a shot, but I don't have a working installation yet (working on
> my first page) and this seemed like a simple question.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
