During vsd->vsdx file conversion, null pointer exception is thrown.
vsd file and callstack:
2023.05.26.zip (7.9 MB)
The file was converted using this code:
File file = new File(PATH_TO_VSD_FILE);
Diagram d = new Diagram(file.getAbsolutePath());
d.save(file.getAbsolutePath() + "x", SaveFileFormat.VSDX);
You get a NullPointerException when trying to convert a Visio .vsd file to .vsdx with Aspose.Diagram for Java using:
File file = new File(PATH_TO_VSD_FILE);
Diagram d = new Diagram(file.getAbsolutePath());
d.save(file.getAbsolutePath() + "x", SaveFileFormat.VSDX);
The exception is thrown inside the Diagram.save call.
The most common reasons for an NPE in this scenario are:
file.getAbsolutePath() returns a string that does not point to an existing file (e.g., the file is missing, the path contains illegal characters, or the program does not have read permission). When the constructor tries to load the document it receives a null stream, which later leads to an NPE."x" to the original path creates a name like C:\folder\myfile.vsdx without a separator (the original name already ends with .vsd). If the original path already ends with .vsd, the resulting string becomes myfile.vsdx (which is fine), but if the original path does not end with a separator, the generated path may be malformed (e.g., C:\folder\myfile.vsdx is okay, but C:\folder\myfile.vsdx when the original string already contains an extension can confuse the loader). Using an explicit output file name removes this ambiguity.File file = new File(PATH_TO_VSD_FILE);
if (!file.exists()) {
throw new IllegalArgumentException("Visio file not found: " + file.getAbsolutePath());
}
String outPath = PATH_TO_VSD_FILE + ".vsdx"; // or any folder you prefer
Diagram d = new Diagram(file.getAbsolutePath());
d.save(outPath, SaveFileFormat.VSDX);
Diagram object:License lic = new License();
lic.setLicense("Aspose.Diagram.Java.lic");
SaveOptions options = new VsdxSaveOptions();
((VsdxSaveOptions)options).setRefreshLayout(false);
d.save(outPath, options);
By confirming the file exists, providing a clean output path, using a recent library version, and optionally disabling layout refresh, the NullPointerException should be eliminated.
If after these steps the exception is still thrown, please share the complete stack trace and the exact Aspose.Diagram for Java version you are using so we can investigate further.
I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.
SDK version unclear — refer to the official release notes before applying this guidance.
@casserolepan
Thanks for the template file.
I have tested your scenario/case using our latest version : Aspose.Diagram for Java v25.11 . It works fine and as expected.
Please find attached the output vsdx file for your reference.
2023.05.26.zip (6.7 MB)
As you can see it works fine with latest version and we could not find any issue, so kindly use latest version. If you still find the issue with latest version, then please share your working environment e.g. operating system, Java version, project type that you are using?We will evaluate your issue further.
The error is indeed gone when converting with the latest version. Thank you, and sorry for the inconvenience!
@casserolepan
It is great that you were able to resolve this issue on your end. In case you have further inquiries or may need any help in future, please let us know by posting a new thread in Aspose.Diagram’ forum.