On Thu, 05 May 2011 13:19:20 -0300, Howard Lewis Ship <[email protected]>
wrote:
I'm beginning to think that we should simply check that the
initialization of any field is an immutable value; we know what main
JDK classes are immutable (String, Boolean, Number) and can have a
service (combined with an @Immutable annotation) go further.
And throw and exception when the field is not immutable? +1!
This is a recurring question on the list, but not one that fits into
an FAQ meaningfully ... I think the framework needs to change.
Yep . . .
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
