We have a application that had modules that use Aspose Words, Slides, PDF, and Cells to support various services. We are in the process of migrating our applications to the cloud. As part of this we need to bundles ALL of our resources used by a microservice into a single fat JAR for deployment to the cloud.
For ALL of these use cases we are able to load the fonts just fine in our legacy environments and in our dev environments. When we package our fonts as resources in the JAR we are unable to load the fonts. We are able to load other resources from the JARs just fine for other parts of our services but are unable to load font files into Aspose.
We have a workaround that we are using that involves extracting the fonts from the jar onto the local disk and then loading them from there but we would prefer to just load the fonts as resources directly from the JAR like we do with all of our other non Aspose resources. This workaround may not work for us long term due to container restrictions.
Is there any way we can fix this OR is it possible that JAR resource loading be added as improvement tickets?