On Wed, 28 May 2014 10:45:06 -0300, Jochen Kemnade
<jochen.kemn...@eddyson.de> wrote:
Am 28.05.2014 15:32, schrieb Jochen Kemnade:
How about ClassMutabilityAnalyzer if we really want to use it for that
single
purpose only?
Or rather ObjectMutabilityAnalyzer (because we actually want to
determine if an *Object* is immutable) and an OrderedConfiguration, so
we can put fast analyzers first.
I guess it'll be rare to actually analyze the mutability of an object and
not of its class, but I can't see why not. :) Please go ahead. ;) I like
the name very much, as it's descriptive and follows the pattern used in
similar services.
Regarding putting the fast (also generic and class-based ones) first or
last, we usually put them last, so the user-contributed ones get used even
if you don't use an ordering constraint, and most people don't know or
forget about it, then the Tapestry-provided ones get called first and the
user provided are never actually invoked. Anyway, even the object-based
ones, which I guess Tapestry will provide none, will be quite fast
already, so I see no need to put the Tapestry-provided first.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
