Println("\tlist invalidated"); } }); strings. addListener(new ListChangeListener() { @Override public void onChanged(Change swap) { method. out. println("\tstrings = " + swap. getList()); } }); process. out. println("Calling add(\"First\"): "); strings. add("First"); process. out. println("Calling add(0, \"Zeroth\"): "); strings. add(0, "Zeroth"); procedure. out. println("Calling addAll(\"Second\", \"Third\"): "); strings. addAll("Second", "Third"); method. out. println("Calling set(1, \"New First\"): "); strings. set(1, "New First"); ultimate List checklist = Arrays. asList ("Second_1", "Second_2"); procedure. out. println("Calling addAll(3, list): "); strings. addAll(3, list); process. out. println("Calling remove(2, 4): "); strings. remove(2, 4); ultimate Iterator iterator = strings. iterator(); whereas (iterator. hasNext()) { ultimate String subsequent = iterator. next(); if (next. contains("t")) { approach. out. println("Calling remove() on iterator: "); iterator. remove(); } } process. out. println("Calling removeAll(\"Third\", \"Fourth\"): "); strings. removeAll("Third", "Fourth"); } } not like the Java collections framework, the place the general public API comprises either the interfaces, corresponding to record and Map, and urban implementations of the interfaces for you to instantiate, akin to ArrayList and HashMap, the JavaFX observable collections framework presents in simple terms the interfaces ObservableList and ObservableMap, yet now not concrete implementation sessions. to acquire an item of a JavaFX observable collections interface, you utilize the application classification FXCollections. In directory 6-1, we receive an ObservableList item by means of calling a manufacturing facility approach on FXCollections: ObservableList strings = FXCollections. observableArrayList(); We then hooked an InvalidationListener and a ListChangeListener to the observable checklist. The invalidation listener easily prints out a message whenever it’s referred to as. The checklist switch listener prints out the content material of the observable checklist. the remainder of this system easily manipulates the content material of the observable checklist in quite a few methods: by way of calling tools at the java. util. record interface, through calling a number of the new comfort equipment extra to ObservableList, and by way of calling the remove() approach on an Iterator bought from the observable record. after we run this system in directory 6-1, the next output is outlined to the console: * * * Calling add("First"): record invalidated strings = [First] Calling add(0, "Zeroth"): record invalidated strings = [Zeroth, First] Calling addAll("Second", "Third"): record invalidated strings = [Zeroth, First, moment, 3rd] Calling set(1, "New First"): checklist invalidated strings = [Zeroth, New First, moment, 3rd] Calling addAll(3, list): checklist invalidated strings = [Zeroth, New First, moment, Second_1, Second_2, 3rd] Calling remove(2, 4): checklist invalidated strings = [Zeroth, New First, Second_2, 3rd] Calling remove() on iterator: checklist invalidated strings = [New First, Second_2, 3rd] Calling remove() on iterator: checklist invalidated strings = [Second_2, 3rd] Calling removeAll("Third", "Fourth"): record invalidated strings = [Second_2] * * * certainly, each name that we made within the code to alter the content material of the observable record brought on a callback on either the invalidation listener and the checklist switch listener.