It appears you are encountering an issue where files are not being generated on disk when using the com.aspose.words.Document#save(java.lang.String, int) method, even though no exceptions are raised. Here are some troubleshooting steps to consider:
Check File Path: Ensure that the file path you are providing to the save method is valid and that your application has the necessary permissions to write to that location.
Disk Space: Verify that there is sufficient disk space available on the drive where you are attempting to save the files.
Antivirus/Firewall: Sometimes, antivirus or firewall settings can block file creation. Check if any security software is interfering with the file writing process.
Logging: Implement logging around the save operation to capture any unexpected behavior or conditions leading up to the save call.
Test with Different Formats: If applicable, try saving the document in different formats (e.g., DOCX, PDF) to determine if the issue is specific to a certain format.
Update Library: Ensure you are using the latest version of the Aspose.Words library, as updates may contain bug fixes related to file saving.
If the issue persists after these checks, consider reaching out to Aspose support with detailed information about your environment and the specific scenarios in which the issue occurs.
Could you please confirm whether you are sure this issue is related to Aspose.Email for Java?
From your description, it seems that the problem occurs when calling com.aspose.words.Document#save(java.lang.String, int), which belongs to Aspose.Words for Java rather than Aspose.Email.
If possible, please share a few more details about your use case so we can make sure your question reaches the correct support team.
You right, my bad. This issue concern Aspose.Words. More precisely it’s this maven artefact we use and cause the issue: aspose-words-25.8-jdk17.jar. This artefact be part of your maven dependencies for:
groupeid com.aspose
artefactid aspose-total
version 25.8
type pom
For your information we return on our previous version: aspose-words-24.12-jdk17.jar yesterday.
Since this question concerns Aspose.Words we recommend continuing the discussion in the Aspose.Words forum section, where the appropriate team can assist you further.
@frjo If possible, could you please provide a simple code that will allow us to reproduce the problem on our side? We will check the issue and provide you more information. Unfortunately, without ability to reproduce the problem on our side it is hard to answer what might cause the problem on your side.