Community
Participate
Working Groups
Its seems as if the AUT does not terminate / disappear from running AUTs view if the OMM has been used / once been active. Stopping the AUT via the toolbar item does seem to work - manually terminating it e.g. via clicking the [x] not. This is easily reproducible e.g. using the SimpleAdder (FX) AUT.
Should be fixed before the standalone release if it seems reasonable risk free.
It looks like the problem originates in the constructor for o.e.j.rc.javafx.listener.MouseMoveDone: * An ExecutorService is instantiated without explicitly specifying a ThreadFactory. * The default ThreadFactory implementation ensures that created Threads will *not* be daemons. * The Executor Thread remains running even after the AUT is ended. It would also be worth looking into whether the ExecutorService should be shut down when Object Mapping Mode (and other modes in which it is used, if any) is ended.
Fixed with: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=00c0a7be940e44fde6fceb788b27bc0c62d10f89 I opted for the daemon thread route beacuse: * the worker threads aren't doing anything that requires that they shut down cleanly, and * the logic for when to start and stop the Executor is not *blatantly* obvious to me.
I´ve tested this with CaA-JavaFX AUT Configuration an Windows 7, on gandalf and on Mac, manually terminating after using the OMM works fine.
Closed due to comment 4.
