On Tue, Sep 2, 2014 at 12:44 PM, nicolas de loof <[email protected]> wrote: > expected @DataBoundSetter to be an alternative to @DataBoundConstructor > (fully removing it)
Sorry, that is not how it is. > @DataBoundSetter applies to fields, so the confusion. As mentioned, it is best applied to setters, but as a convenience can also be used on fields. > I prefer to avoid setters to reduce code verbosity. Sure, it is less verbose, but you are in trouble if you ever need to refactor things and someone else had started to refer to your fields directly. (You can escape using @AdaptField, but better to not put yourself in this situation to begin with.) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
