>From a "keep close to the code" perspective, you can override
finishLoad() and set the propertie's initial value there.  Setting the
property from finishLoad() becomes the default value (i.e., instead of
null, 0 or false) to which it is reset at the end of the request
cycle.

On 7/18/05, Hugo Palma <[EMAIL PROTECTED]> wrote:
> It's really cool that we don't need to have the property element in the
> xml to configure a property but it's a shame that we can't specify an
> initial value of the property in the annotation. Just because we have an
> initial value we have to create a configuration file with the property
> element.
> It would be great if it was provided an annotation for providing an
> initial value for a property.
> 
> What do u think ?
> 
> Cheers
> 
> Hugo
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

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

Reply via email to