Why is almost everything in the API final
Fabrizio.Giudici at tidalwave.it
Tue Sep 3 10:34:26 PDT 2013
On Tue, 03 Sep 2013 17:49:10 +0200, Richard Bair <richard.bair at oracle.com>
> Or, when co-bundling the JRE with your app, you can provide whatever
> workaround you need to your copy of the JRE (just remove final from a
> few places or whatnot). Of course the cost comes when you need to
> upgrade to a newer version of FX, but if you gotta resort to one evil or
> another for the sake of shipping, this one at least leaves you in
I add that since it has been said that, unlike Spring, JavaFX 2 is more
designed for composition in place of inheritance, let's rather focus on
verifying that there's a good design in this sense and eventually ask for
a better one when needed. I mean, rather than subclassing, perhaps that
quick fix can be done by composition?
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - fabrizio.giudici at tidalwave.it
More information about the openjfx-dev