@mariofelesdossantosjr Configuration should be identical to the jdbc demo project I just created: https://github.com/edvin/tooldb

Do I really need to get do conversion between object mapped by hibernate to property object fx?

@mariofelesdossantosjr You might be able to annotate getters/setters instead of the property though. That would be interesting to try for sure.

@Carlton Whitehead From IDEA: "rounds = 1\norg.junit.runners.model.TestTimedOutException: test timed out after 10 seconds"

I don't understand everything going on with respect to Mock, so I'm not sure how to debug

@edvin Do you have the database script ?

@mariofelesdossantosjr What do you mean by database script?

@mariofelesdossantosjr Do you mean the schema?

yes

I'll dump it and add to the repo when I get home 🙂

ok

Thanks

I'll try refactoring it without the mock library and see if that helps

That test could fail with a timeout if the mock never received its expected call, or the mock library somehow fails to record the invocation, or maybe if the device is just really slow. So that should at least help rule out one of those cases

@edvin @Carlton Whitehead Is the test running on a test runner thread and simply queuing up Platform.runLaters? If that's the case, it might not be invoking the latch countdown right away. You hit await with a bunch of pending mouse events but not a guarantee that they're going to be serviced immediately.

@carlw I think you might be onto something. There could also be room for an FX event loop issue. I'll take a look at that too

@carlw @Carlton Whitehead Thanks guys 🙂 Let me know what you find. I'll start working on a Hibernate example in the mean time.

@carlw and @edvin I refactored the test to avoid the mocking library, and await the latch from an FX thread. How does this look?

@edvin is there a way to use tab pane with view classes instead of passing in a node?

@chrbongardt Sure,

add<SomeView>()

I see

The title will be picked up automaticaly. You can also override or assign to the

closeable

property and it will be picked up as well

thats nice, thanks

@Carlton Whitehead @edvin I'm skeptical of the timing of that test. When I'm looking at FX code, I pretend that runLater() could take a minute and see where there could be a problem. While I totally expect my button press to be invoked within milliseconds, there might be some optimizations put in such as "don't do any FX event processing until there's a visible window with dimensions >0". I don't know of such an optimization off hand, but the potential is there.

@carlw That's a very good point

Hmm.. isn't

@Transient

supposed to make JPA/Hibernate ignore a field?

yes. what are you seeing ^

Another possible issue just occurred to me. I wonder if the latch is getting its

countDown()

call prior to the

await()

? Maybe that's re-stating what Carl just said?

Hibernate is saying

Could not determine type for: javafx.beans.property.SimpleIntegerProperty, at table: Vendor, for columns: [org.hibernate.mapping.Column(idProperty)]

The really weird thing is that this field is final, so Hibernate should ignore it for that reason alone.