This is some JavaFX dependency injection code I use for an app that signs code, removing any old signatures. It also saves the commands and encrypts the credentials. It's a small app so no extra scopes are needed.

@User uploaded a file: DI Used in a JavaFX App and commented: Unit tests swap out the main DAO, "ConfigurationDataSource"

@edvin to you want me to share the presentation you asked for here? or mail it to you?

@ron Could you email it to me? es@syse.no

will do its only 7 slides

gmail

I have a question about TableView

onEditCommit

. I have configured some columns using the

TextFieldTableCell.forTableColumn()

call to make them editable. When I edit the textfield and hit enter, the changes are flushed back into the underlying domain object. However, If I configure an

onEditCommit

handler for the tablecolumn and do nothing in that handler, my data is not changed anymore. It seems like I inherit the responsibility to update my data if I override

onEditCommit

, is that correct`? I just want a listener to fire when a commit is performed, I don't want to manually put the data back into my domain object. @carlw I bet you've blogged about this once or twice? 🙂

(I know how to update the data in

onEditCommit

but I don't know why I inherit this responsibility when I configure a commit listener)

@ron Perfect slides, just what I needed. I'll shamelessly copy most of your points if that's OK? 🙂

sure go ahead

what are you going to do with them?

(just curious)

They are btw still debating if the recordings of the talks will be made public, as clients names were mentioned

I'm going to muster up some courage and start doing talks on TornadoFX

ROFL I was talking about sending a request to do a tornadofx talk for Devoxx in Belgium 🙂

@ron Oh, do it!!

@edvin - you are correct in you interpretation of

onEditCommit

behaviour

@gtnarg Thanks. Is there a way to call

super()

or perform the usual operation without spelling it out explicitly?

I basically had to do this:

@User uploaded a file: Untitled

As I understand it, if I don't override

onEditCommit

, those two lines are performed automatically for me. I just want to do the last line, calling må controller function.

It is very important to note that if you call TableColumn.setOnEditCommit(javafx.event.EventHandler) with your own EventHandler, then you will be removing the default handler. Unless you then handle the writeback to the property (or the relevant data source), nothing will happen. You can work around this by using the TableColumnBase.addEventHandler(javafx.event.EventType, javafx.event.EventHandler) method to add a TableColumn.EDIT_COMMIT_EVENT EventType with your desired EventHandler as the second argument. Using this method, you will not replace the default implementation, but you will be notified when an edit commit has occurred.

from the javadoc - sorry not sure how to quote it...

@gtnarg Perfect, just what I needed. And I should have guessed this myself. I see in the code that my handler isn't added to a list, it's writing to a property that can only contain one entry. But I think it's weird that the CellEditEvent passed in can't handle this, or that they didn't provide a

CellEditFeatures

object like they do elsewhere.

it's not intuitive - that's for sure - took me a long time to figure it out when I first ran into it...

@gtnarg Do you know if I can listen for an edit commit event on the TableView or do I need to listen on each column?

pretty sure it's on each column

but that's an off the cuff answer 🙂

The

EDIT_COMMIT_EVENT

seems to be private in JavaFX 8

I can get to it using

TableColumn.editCommitEvent()

it seems. Weird choice.