This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Regression. Jemmy can't be used on displays like "Reflection" on Windows, because it always starts awtRobot. #Exception in thread "main" java.lang.ExceptionInInitializerError # at org.netbeans.jemmy.drivers.InputDriverInstaller.install(Unknown Source) # at org.netbeans.jemmy.JemmyProperties.setDispatchingModel(Unknown Source) # at org.netbeans.jemmy.JemmyProperties.initDispatchingModel(Unknown Source) # at org.netbeans.jemmy.JemmyProperties.initDispatchingModel(Unknown Source) # at org.netbeans.jemmy.JemmyProperties.init(Unknown Source) # at org.netbeans.jemmy.Test.run(Unknown Source) # at org.netbeans.jemmy.Test.run(Unknown Source) # at com.sun.forte.performance.testing.MyConvenientTestExecutionClass.main(MyConvenientTestExecutionClass.java:8) #Caused by: org.netbeans.jemmy.JemmyException: Exception during java.awt.Robot accessing # at org.netbeans.jemmy.drivers.input.RobotDriver.<init>(Unknown Source) # at org.netbeans.jemmy.drivers.input.KeyRobotDriver.<init>(Unknown Source) # at org.netbeans.jemmy.drivers.InputDriverInstaller.install(Unknown Source) # at org.netbeans.jemmy.drivers.DriverManager.<clinit>(Unknown Source) # ... 8 more For similar problem see IZ 30537.
I have a similar problem running on xservers which don't support the XTEST protocol. In theory I should be able to run in event mode but an exception is always thrown in the robot driver install.
Correct solution of this problem consist in rewriting driver registration procedures. It will be done one day, but, from now, it's hard to say when. Meanwhile, I can propose a simple fix (it's rather a temporary solution) which consist in using of "lazy initialization" of java.awt.Robot instance inside RobotDriver. I've checked - it's working, unless, naturally, you use some features which requires Robot directly: PNGEncoder, image package or drivers for AWT components. Next update will contain the changes.
Changes described in my previous comment done in 2.2.4
This is issue was fixed in version 2.2.4 of Jemmy. Closing, but if it is necessary, please reopen and attach a test case.