Creating a new profile and loading from a source that is not in OneDrive seems promising (I'm still testing and have a few other issues to sort out with the new profile before I can report results - such as references to missing panel icons, some exception about a duplicate ID in the signalhead tag etc.). I don't see why the program would have an issue with OneDrive, and if so, it should be fixed.
?
Meanwhile, going back to Bob's wish to investigate the underlying issue, I looked again at the exception stack trace (I admit I haven't browsed the source code yet). For an automated swing XML file load and deserialization, where the path is known apriori, I see no reason to use the JFileChooser mechanism. It is designed to let users browse and select files and requires certain resources to be available. Can this file be opened using the file system and the stream handle to be handed to swing to deserialize? In fact, I found the following which seems to be very similar and reporting the same exception:
?
?
This is reported as a Java bug (at least for 1.8). Hence my conclusion is to avoid using JFileChooser in scenarios that do not mandate it.
?
Regards,
?
Gil
Gil Fuchs