Fatal error when resource cannot be resolved

[Daniel Zwolenski]

Me too. 

It would be kind a nice to have a pluggable resource provider in FXML.  An interface we can implement, with the default delegating to resourcebundle. 

Then we could pull resources from other locations (eg database, XML, etc). 



On 21/08/2012, at 6:16 AM, John Hendrikx <hjohn at xs4all.nl> wrote:

> With ResourceBundle, I always will write somekind of wrapper around it that catches that MissingResourceException and provides a default text...
> 
> On 20/08/2012 16:12, Richard Bair wrote:
>> I couldn't agree more. I have had such bugs find their way into production, and the problem is that it isn't found at build time, but at runtime, and results in a complete application failure. Or tons of try/catch code. It is better to have a messed up label than to fail at runtime (although logging a warning or error to the console seems entirely appropriate).
>> 
>> RIchard
>> 
>> On Aug 20, 2012, at 5:50 AM, Werner Lehmann wrote:
>> 
>>> 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.
>>> 
>>> Werner
>>> 
>>> 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?
>