I was reading section 3.5.3 Specifying properties in the page specification
of Tapestry in Action and then realized that writing something like:

<property-specification name="item" type="examples.todo1.ToDoItem"/>

Doesn't add anything to:
(In the page class)
public abstract ToDoItem getToDoItem()

So the property-specification should be optional here. Reflection should
understand that if somebody declared a get/set abstract in a page class
that's very probable that the goal was to have a property with the declared
type. 

To specify persistent attribute and default value, annotation could be used.
Which annotation in this list
(http://jakarta.apache.org/tapestry/tapestry-annotations/index.html) is used
in Tapestry 4.0 for that? 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to