I have got a question about "<property-specification>" handling.
In my ".page"-specification I declared the following:
-------------------------
<page-specification class="foo.RegisterFormPage">
<property-specification name="customer"
persistent="no" type="foo.CustomerDTO" initial-value="new
foo.CustomerDTO()"/>
...
</page-specification>
-------------------------
The property accessor/mutator method in "foo.RegisterFormPage" are
declared as abstract and no member-variables are defined.
-------------------------
abstract class RegisterFormPage extends BasePage
{
...
public abstract CustomerDTO getCustomer();
public abstract void setCustomer(CustomerDTO customer);
...
}
-------------------------
Currently I am never invoke "setCustomer(null)" anywhere in my source to
explicitly reset the property and it seems to work fine.
On the other hand I have read that "initial-value" is only evaluated
once while page loading and never again.
Could this lead to multi-threading issues when not invoking
"setCustomer(null)" manually or is this automatically prevented by
tapestry.
thanks
Jan Zimmek
