Free Support Forum - aspose.com

Instantiation problem in OSGi environment on MS Windows


#1

Hi,

I have a problem with the instantiation of a document when the code runs in OSGi environment under MS Windows OS. This problem started to occur when I switched to Aspose.Words for Java 18.8. With 18.7, issue can’t be reproduced.

I’ve tested on Windows 7 x64 with Java 1.8.0_181 and Windows Server 2008 with Java 1.8.0_101.

Here’s the exception:

java.lang.IllegalStateException: File C:\Users\User\AppData\Local\Temp\1536065047283-0\org.eclipse.osgi\63\0\bundleFile\resources\WindowsNativeCall_x64.dll is not exist.
	at asposewobfuscated.zz2Q.zzZ(Unknown Source)
	at asposewobfuscated.zz2Q.zzzR(Unknown Source)
	at com.aspose.words.WindowsNativeCall.<clinit>(Unknown Source)
	at asposewobfuscated.zzA1.<clinit>(Unknown Source)
	at asposewobfuscated.zzC1.zzU(Unknown Source)
	at asposewobfuscated.zzC2.zzQK(Unknown Source)
	at asposewobfuscated.zzRF.zzZ(Unknown Source)
	at asposewobfuscated.zzRZ.zzQN(Unknown Source)
	at asposewobfuscated.zzRZ.zzS(Unknown Source)
	at asposewobfuscated.zzRZ.zzT(Unknown Source)
	at com.aspose.words.FontSettings.zzT(Unknown Source)
	at com.aspose.words.zz97.zzR(Unknown Source)
	at com.aspose.words.zz97.zzQ(Unknown Source)
	at asposewobfuscated.zzR3.zzZ(Unknown Source)
	at com.aspose.words.zzZ36.zzZpA(Unknown Source)
	at com.aspose.words.zzZ21.zzZo9(Unknown Source)
	at com.aspose.words.zzZ21.zzZoa(Unknown Source)
	at com.aspose.words.zzZ21.read(Unknown Source)
	at com.aspose.words.Document.zzY(Unknown Source)
	at com.aspose.words.Document.zzZ(Unknown Source)
	at com.aspose.words.Document.<init>(Unknown Source)
	at com.aspose.words.Document.<init>(Unknown Source)

I’m just instantiating Word document inside an Pax-Exam test:

Document document = new Document("basic.doc");

This also happens for lot of .rtf files. Please find the files attached.

Can you check this?

Thanks,
Zeljko

files.zip (774.9 KB)


#2

@Zeljko

Thanks for your inquiry. We have tested the scenario at Windows 10 and have not found the shared issue. Please spare us some time to investigate this issue on Windows Server 2008. We will investigate this issue and share our findings with you.


#3

Hi Tahir,

I’ve tried to execute the test on Windows 10 Pro 64bit with Java version 1.8.0_181 and it still fails with the same exception.

Regards,
Zeljko


#4

@Zeljko

Thanks for your inquiry. Could you please share the following detail here for testing:

  • Please create simple OSGI application that helps us to reproduce your problem on our end and attach it here for testing.
  • Please share the steps that you are following for this issue.

As soon as you get these pieces of information ready, we will start the investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip and upload them.


#5

Hi Tahir,

Please find exported eclipse project attached. You can import it into your workspace and run the test /AsposeWordsOsgiTest/src/test/java/osgi/test/OsgiTest.java.

Thanks,
Zeljko


#6

@Zeljko

Thanks for sharing the detail. Unfortunately, we are unable to download the shared file. Please upload the ZIP file to Dropbox or any other file hosting service and share the download link here. Thanks for your cooperation.


#7

Hi Tahir,

Please try this link: https://we.tl/t-AMcqIuehiz

Regards,
Zeljko


#8

@Zeljko

Thanks for sharing the detail. We are working over your query and will get back to you soon.


#9

@Zeljko

Thanks for your patience.

We have imported the shared project in Eclipse Kepler, unfortunately, it is not imported correctly. Could you please share the Eclipse version that you are using? Please also share the step by step guide that helps us to reproduce this issue at our end. Thanks for your cooperation.


#10

Hi Tahir,

I’m using Eclipse Version: Oxygen.2 Release (4.7.2).

You should import the archive file by clicking on File > Import > General > Existing Projects into Workspace > Select archive file > Browse.

After the project has been imported, you should invoke mvn clean install either through Eclipse or command line. Clean install should fail during the test phase with the exception from the first post. After that, you should invoke mvn eclipse:clean eclipse:eclipse and you’ll be able to run the test like any regular JUnit test.

Regards,
Zeljko


#11

@Zeljko

Thanks for sharing the detail. We have imported the shared project in Eclipse Oxygen 2. The Jar file org.eclipse.equinox:org.eclipse.equinox.ds:jar:1.4.101.v20130813-1853 is missing. It is not importing in the project. Could you please ZIP and attach this Jar file? We will add it manually and test this issue. Thanks for your cooperation.


#12

Hi Tahir,

You can download the jar file from the Maven repository:
https://mvnrepository.com/artifact/org.eclipse.equinox/org.eclipse.equinox.ds/1.4.101.v20130813-1853
or
use direct link: http://dist.wso2.org/maven2/org/eclipse/equinox/org.eclipse.equinox.ds/1.4.101.v20130813-1853/org.eclipse.equinox.ds-1.4.101.v20130813-1853.jar

Regards,
Zeljko


#13

@Zeljko

Thanks for sharing the detail. We have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSJAVA-1897. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.


#14

The issues you have found earlier (filed as WORDSJAVA-1897) have been fixed in this Aspose.Words for .NET 18.10 update and this Aspose.Words for Java 18.10 update.


#15

Hi, I’m still having an issue with this. I’m using latest aspose for words 19.2

project: https://wetransfer.com/downloads/d6baaf20529ea26f470028f1e454276820190313145701/e6c8ae7898c6b32d57a78b1c1f60da9520190313145701/d5e690

Can you please check this again?

Thanks,
Zeljko.


#16

@Zeljko

Could you please try the latest version of Aspose.Words for Java 19.3? Please let us know if you still face problem. Thanks for your cooperation.


#17

Hi, I have tried it and I’m still having the same error.


#18

@Zeljko

Thanks for sharing the detail. We have logged this problem in our issue tracking system as WORDSJAVA-2008. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.