Aspose .total for java 使用过程中存在水印问题

license已在4.9号过期,但是没有更新版本仍然使用的是旧的版本23.3,可是pdf文件使用过程中出现了水印,这个问题如何解决?

@xia_ziwei,

哪个 Aspose Java API 在输出文档中嵌入水印?请确保您使用的是在订阅到期日期 (2024-04-09) 之前发布的 Aspose (Java) API 官方版本。此外,我们建议您检查以下几点以追踪并解决您的问题:

  1. 在 Aspose.Total for Java 中为不同 API 实例化和定义 License 对象时,使用完全限定的命名约定。另外,请确保在应用程序/程序启动时执行对 setLicense 的调用。请在编辑器的调试器中单步执行。
  2. 确保您的代码不会捕获许可代码中 Aspose API 抛出的异常。例如,如果 Aspose API 找不到许可证或者许可证已过期,无法与较新的 API 版本一起使用,则 Aspose API 将抛出异常/消息。
  3. 确保输入文档没有评估消息或水印。
  4. 确保在实例化任何其他对象之前执行 API 的 setLicense 方法。

Hi Amjad:

Thank you for your reply. We purchased a perpetual license last year. From my understanding, the word “perpetual” means that this license will never be expired as long as we keep using the current version 23.3. However, on the date of subscription expiry, Apr 9th, the watermark shows on each files we transferred.

Before that, we had a AEM product version upgrade from 6.5.12 to 6.5.20 on March 31st but the license is still working till Apr 9th. To check if the issue is caused by AEM upgrade, we also tested the license in our backup environment (AEM 6.5.12), the watermark issue still exists. However, we attempted to change the local time back before the subscription expiry date, the watermark disappeared. This is not what we want when we purchased the “perpetual” license if nevertheless the license will be expired someday.

Also, I am a little confused about the definition of “Singleton” or " Set up license for multiple times". Do you mean that if there are product upgrades or new function launchs and we have to reload the license again even for the same server same person, this can be treated as a new “set up”?

Thank you.

@Jillianliu,

Your understanding is correct. However, you may be using a newer version that was released after your subscription expiry date.

I guess by “AEM product version” you meant the version of Adobe Experience Manager (AEM), is that correct? Anyways, Aspose APIs are not affected by any third-party tools, apps, or libraries whatsoever.

Is your application being used in a multi-threaded environment where you are using/setting your license in threads for different users? We recommend users, if not necessary, process the licensing code only once at the beginning of the application’s life cycle. Therefore, ensure that the license settings code is placed outside of the thread(s) so that the license can be set only once at the start of the application. The code for setting the license should not be executed repeatedly and concurrently in threads, as this is not necessary may create problems.

In any case, if you still encounter the issue and are unable to resolve it, we will need your sample (Java) program and license file. Please note that when sending us your license file, use a private message. Do not attach the license file to this post. Send the license file via private message. Please refer to the document and follow the guidelines provided on how to send license file.

Once we receive your license file, we will start evaluating your issue on our end.

Hi Amjad:

Thank you so much for your reply. To understand the problem caused by multi-threaded environment, do we have a limitation that the license can only be used for one server one person? If there is another server with different ip but in the same environment, will this cause issues?

Warm regards
Jillian

@Jillianliu,

Generally, there are no restrictions set forth by the license file itself. However, it may depend upon your license type. Different license types have different attributes, restrictions, and capabilities. You can reach out to our sales team in the Aspose.Purchase forum regarding your license type for complete reference.

Moreover, as requested earlier, please share your sample (Java) program and license file to reproduce the issue on our end. Please note that when sending us your license file, use a private message. Please refer to the document and follow the guidelines provided on how to send license file.