tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>
Subject Re: [jira] [Closed] (TAP5-1520) ConcurrentModificationException while modify unclaimed private collection from different Threads
Date Thu, 05 May 2011 17:07:50 GMT
On Thu, 05 May 2011 13:19:20 -0300, Howard Lewis Ship <hlship@gmail.com>  
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message