We are currently evaluating Aspose.Words (Java) and it seems like the startup time (before even looking for the license) is taking a considerable amount of time.
The steps we have performed:
1) Imported the Aspose.Words 14.5.0-jdk16.jar into a local Maven respository.
2) Included the dependency in our POM (compiled scope)
3) A static initializer to read and load the license file.
Before even getting to the static initializer Jetty will hang for almost 3 minutes before continuing on to loading the license file.
If we take the dependency out of Maven, Jetty starts up fine in a matter of seconds.
The environment we have now is:
- VirtualBox VM
- Jetty
- JDK7
- Google Guice and Guava
- Maven
As an additional note, if I run the license check in a JUnit it appears to run fine.
Is this startup time normal because it makes continual local develop-deploy-test cycles considerable inefficient to run?