JDK 8 and properties
Llewellyn Falco
isidore at setgame.com
Thu Oct 13 12:01:44 PDT 2011
> Simply generating the getter, setter, equals and hashcode is only part
> of the problem. There also need to be a way to enumerate/loop over the
> properties. Without this, each framework will continue to write their
> own "bean introspector".
I use C# for about 1/2 of my development time.
As such I have a lot of experience with properties.
And I wanted to quickly disspel the idea that properties remove getters&setters
they do not.
You will still get many situations where a getter and setter is
preferred or required.
especially when a Conversion is in play, such as
setLengthInMeters(meters)
or
getAverage(includeExtraCredit, includeTransfers)
In general, I am not a Fan of properties, although I am VERY
supportive of a syntax like lombok to reduce the clutter and
boilerplate.
because the Properties split up and then you have to deal with the
getters/setters anyways. you will always need a bean introspector.
probably somethings like
getMethods().where(m->m.getName().startsWith("get")
--
Llewellyn Falco
www.approvaltests.com
www.teachingkidsprogramming.org
More information about the coin-dev
mailing list