A crash triggered by absent "LDAPConnectionOptions"

[Sargis Simonyan]

Hi Peter,

I am testing at the moment the uploading the key to server according to described routine:

https://www.didisoft.com/java-openpgp/examples/exchange-keys-with-pgp-ldap-servers/#upload

I will describe the issue much detailed if it is needed, but the error thrown is about missed class. You have made many changes last time, so maybe this left from library?

06-13 21:59:41.768: E/AndroidRuntime(27671): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.unboundid.ldap.sdk.LDAPConnectionOptions" on path: ....

[Sargis Simonyan]

one note, I tested this routine before, it is not working after updating of the downloaded module. The library jars of course are attached as they should to be ....

[DidiSoft Support]

Hi Sargis,

Here the problem is again missing JAR file (java.lang.ClassNotFoundException)

I will prepare and send you detailed documentation how to load the dependent JAR files with the library in your Android app.

Kind Regards
Peter Kalef
Technical Support
DidiSoft Inc | Toll free (USA and Canada): 866-253-7568 | International: +1-501-313-0397 | Fax: +1-501-313-0397 | Web: www.didisoft.com

--
You received this message because you are subscribed to the Google Groups "DidiSoft Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to didisoft_foru...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sargis Simonyan]

well, the exception type is of course known to me and it is strange that this error happened. And it also tested on previously worked demo. Is there something special to do? I am using jar libraries always, it is a simple routine. But maybe there is really something passed through. We'll see.

Sometimes simple recompilation after cleaning can help. Though I made it several times and in this case it didn't help. 

I will continue tests tomorrow too also and write back if this strange error will be solved.

[Sargis Simonyan]

ok, I removed completely the jars, added from new and rebuild project. Error vanishes. Strange Eclipse stuff, nothing to do with DiDi Soft :)

This issue could be considered as closed.