No Exporter Found if you don't specify a file extension

[vitki@…]

If you download OSM data from the server, and then do a "file/save", or a "file/save as" JOSM gives the error "No Exporter Found! Nothing saved." if you don't specify a file extension.
If you specify the file extension, the save is successful.

[anonymous]

files will be saved as filename.osm

only if your input name is filename. (ends with a point) or an other undefined file extension you will get an exception. (same with latest)

[Leigh]

Just had the same issue - I didn't specify filename., but filename instead - i.e. there was no trailing period, or file extension.

Specifying filename.osm resolves the issue.

See also #7843 for related issue, and steps to reproduce.

[ingalls]

In my opinion it would be best to change this behavior! For a new user that could become very confusing. Wouldn't it be best just to append .osm on all files unless otherwise specified? That way the file is saved in the OSM format by default and if the user wanted it in another format they could specify it?

[Don-vip]

I can't reproduce this bug, it works fine with:

Java version: 1.6.0_37, Sun Microsystems Inc., Java HotSpot(TM) 64-Bit Server VM
Operating system: Windows 7

and:

Java version: 1.7.0_07, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Operating system: Windows 7

What's your system info ? Do you really have this bug as explained in the description ?

[ingalls]

Yeah it is the strangest thing. I don't have the stats for the computer that is having the error. My iMac runs it just fine, no errors when saving - .osm is appended automatically!

On my windows 7 machine this is not the case "No exporter found" is thrown up unless I specifically add .osm. I was quite worried when I first saw it as I had a couple hours work and no network connection! But after a bit of searching I came accross this. I will get the OS & Java stats tomorrow morning when I get access to that computer again.

[ingalls]

I'm going to close this and move the discussion to #7843 so not to fragment the conversation between two places.