Hi Andy,
It is unlikely that we will undeprecate the builders but more likely
that we could make them available as a separate download so that people
that wanted to use them could still use them.
Martin will follow up with you. Essentially, we would accept changes
that were backward compatible to the deprecated builders.jar that we
make right now, but we are not interested in taking the builder code
base forward ourselves at this time.
Steve
On 2013-10-30 8:25 AM, Lesley Perkins wrote:
In case it wasn't clear, I'm submitting this to the JavaFX team in hopes that
we can UNdeprecate the builders in Java 9. Is this a possibility?
--Andy
-----Original Message-----
From: openjfx-dev-boun...@openjdk.java.net
[mailto:openjfx-dev-boun...@openjdk.java.net] On Behalf Of Lesley Perkins
Sent: Thursday, October 24, 2013 8:00 PM
To: 'openjfx-dev@openjdk.java.net'
Subject: JavaFX Builders, possible solution
I briefly discussed the builder deprecation with Richard when he visited our
company back in May. One of the ways he said to test any solution would be to
build a library jar with the test hierarchy, then build a client jar using the
library jar, then change the hierarchy in the library code and run the client
jar against the new library jar without re-compiling the client jar.
I have done that, and it works in my simple test:
BuilderLibA - is the "original" builder library (my version)
BuilderClient - is the client app (main class is
com.cpex.javafx.test.BuilderClientTest), built against the BuilderLibA.jar.
BuilderLibB - I have inserted a new class in the hierarchy between
RegionBuilderBase and ParentBuilderBase.
I had tested the solution in both JDK 7 and JDK 8, a few months back, and then
forgot about it as several other things came up. All of the code has been
uploaded to DropBox:
https://www.dropbox.com/sh/fs8o105bvmr4s2k/ze-hJssiHC
If there is something else that I'm missing in this issue let me know...I
really hate to see builders go away.
--Andy
This message may contain confidential information and is intended for specific
recipients unless explicitly noted otherwise. If you have reason to believe you
are not an intended recipient of this message, please delete it and notify the
sender. This message may not represent the opinion of IntercontinentalExchange,
Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract
or guarantee. Unencrypted electronic mail is not secure and the recipient of
this message is expected to provide safeguards from viruses and pursue
alternate means of communication where privacy or a binding message is desired.
