2010/4/13 Filip Hanik - Dev Lists <[email protected]>: > This makes zero sense and I would do a -1 on this commit and the bug in > general. > What effectively has happened here is that there has been a public API > change without any justification. > > Since this is a mutable field, you've now made it non mutable. and in there > lies the change. >
I am +1 on the change. If we need it configurable, let's define a system property to initialize its value at startup, or better to define an instance field somewhere. It makes no sense for me to flip between "secure random" and "insecure random" at runtime. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
