Closed winnall closed 6 years ago
Hi,
thanks for the report. That seems like an OSGI related issue. I've found a blog post that seems to describe this issue a bit further: http://blog.admadic.com/2013/03/javafx-fxmlloader-with-osgi.html
Can you maybe try to call
FXMLLoader.setDefaultClassLoader(AboutStageBuilder.class.getClassLoader());
before calling menu = menuToolkit.createDefaultApplicationMenu("ABC");
and see if that solves the issue?
Thanks for the swift response. This makes sense (threads and classloaders tend to be a problem where JavaFX meets OSGi) but I can't test it at the moment (big ongoing refactorisation). I'll get back to you when I've tried it out.
Steve
On 27 Jan 2017, at 11:54, Jan Gassen notifications@github.com wrote:
Hi,
thanks for the report. That seems like an OSGI related issue. I've found a blog post that seems to describe this issue a bit further: http://blog.admadic.com/2013/03/javafx-fxmlloader-with-osgi.html
Can you maybe try to call
FXMLLoader.setDefaultClassLoader(AboutStageBuilder.class.getClassLoader()); before calling menu = menuToolkit.createDefaultApplicationMenu("ABC"); and see if that solves the issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I am using NSMenuFX 2.1.4 in an OSGi (Felix 5.4.0) application with JDK 1.8.0_76-ea on an iMac running macOS Sierra 10.12.3. Other relevant software involved: NetBeans 8.2, Maven 3.3.3.
After a call to
menu = menuToolkit.createDefaultApplicationMenu("ABC");
I get the following stack dump:The bundle is loaded and active: