Search   Recent Topics     Member Listing   Register /  Login 
JDK7 Issue
Forum Index -> General Issues
Author Message

Joined: Nov 21, 2011
Messages: 5

I am evaulating JCAPI and found that if I build and run under JDK 1.7.0_01, the JCAPI fails to initialize. If I switch to 1.6, it works fine. It seems to be the same error as the FAQ on Windows 2008/DEP references but I cannot locate a simple disable-DEP option in Windows 7 (and I really don't want to have to tell all my users to disable DEP for thsi app).

I am using 32-bit Windows 7 fully patched. My test code to this point has only run 1 line of code:

Provider provider = new JCAPIProvider();

Can you offer any suggestions on this? In the meantime I'll proceed to evaluate with Java 1.6.

Exception in thread "main" java.lang.ExceptionInInitializerError
at com.mychoiceid.jcapitest.App.initProvider(
at com.mychoiceid.jcapitest.App.main(
Caused by: C:\Users\redacted\AppData\Local\Temp\JCAPI32.dll: Invalid access to memory location
at com.pheox.jcapi.j.a(Unknown Source)
at com.pheox.jcapi.JCAPIProvider.<clinit>(Unknown Source)
... 2 more

*** EDIT ***
I attached a copy of the output of my app running under JDK1.6 including the output from JCAPIUtil.getEnvironmentInfo()
Under JDK1.7, it crashes as soon as I call any function in JCAPIUtil, so I cannot output those details.

 Description JDK 1.6 Test Output Download
 Filesize 6 kb
 Downloaded:  795 time(s)

Pheox Support

Joined: May 30, 2005
Messages: 148


The problem you have is due to the third party obfuscation tool that we use for JCAPI. We have updated the tool to resolve your problem.
You can find a new jcapi.jar build attached to this post.

We'll fix a new official release soon.

Let us know if you have any other problems.


 Description Download
 Filesize 349 kb
 Downloaded:  327 time(s)


Joined: Nov 21, 2011
Messages: 5

This appears to have resolved the issue. Thanks.
  Forum Index -> General Issues
Go to: