Comments on: My Changes Don’t Happen! — A Java Puzzler

By: Anonymous

Anonymous — Sat, 19 Dec 2009 01:42:13 +0000

I am wondering about your ‘Effect’ section. Since the name, description or userId never got assigned to ‘feature1′, the save should effectively fail right there. May be the ‘feature1′ should be constructed as,

Feature feature1 = new Feature(name, description, userId);

Ignore if this was nitpicking but do let me know if I am missing something here.

By: Ben Northrop

Ben Northrop — Thu, 10 Dec 2009 20:06:39 +0000

Agree about the code bloat…

It would’ve been nice if final was the default in Java, and we could override this to make a method param “unfinal” in the rare case where we wanted to reassign it. Sigh.

By: Jim Kiley

Jim Kiley — Wed, 09 Dec 2009 20:08:11 +0000

Having Eclipse do it by default is handy. I wish it didn’t bloat the source code so much, but after brainos like the one above I’m beginning to think it’s worth the bloat.

By: Carsten Ringe

Carsten Ringe — Wed, 09 Dec 2009 20:04:22 +0000

Recently I’m adding final to my code all over the place. It is so useful to avoid strange effect like the one you described, but it bloats the code even more. I think I’ll set up my Eclipse to add this modifier by default when creating new methods…