[
http://issues.apache.org/jira/browse/TAPESTRY-426?page=comments#action_12320274
]
Sébastien Tardif commented on TAPESTRY-426:
-------------------------------------------
If it's true that the main feature of annotation is too keep related code
together and that Tapestry declared properties was mainly to have an automatic
cleanup ( reset initial value ) it then become a very strong argument to be
able to set initial value of properties using annotation.
By context it should be clear what do those annotation before a property:
@Bean(initializer = "maxRetries=3")
or
@Bean(initializer = "maxRetries=ongl:'1+2' ")
or
@InjectObject("MyHivemindPropertyInstance")
public abstract MyPropertyClass getSessionPersistentProperty();
> Property initial value annotation
> ---------------------------------
>
> Key: TAPESTRY-426
> URL: http://issues.apache.org/jira/browse/TAPESTRY-426
> Project: Tapestry
> Type: New Feature
> Components: Annotations
> Versions: 4.0
> Reporter: Hugo Palma
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
