Fatal error when resource cannot be resolved

Werner Lehmann lehmann at media-interactive.de
Mon Aug 20 05:50:51 PDT 2012

Well, a simple localization typo can cause this. We usually don't have 
the resources (manpower :-) to test the whole application after 
localization. I'd rather have the customer see a wrong label text than a 
complete failure because the fx panel is gone, forcing us to provide an 
update ASAP.


On 20.08.2012 14:33, Greg Brown wrote:
> This is a pretty easy exception to resolve. Why not just add the
> missing key to your resource bundle?

More information about the openjfx-dev mailing list