Re: [Wrapper-user] Wrapper ActiveX Integration

[Leif M. <lei...@ta...>]

Seamus,
What are you seeing when you try running the devicemanager.exe binary?
When running under the Wrapper, it will by default set the working
directory to the location of the Wrapper.exe.  This may be affecting the
way your exe is locating its DLLs.  My first guess is a PATH or other
environment variable issue.
Please try to get it working as a console app first.
Then and only then move on to getting it working as a service.  I say this
because there are a number of additional security and environment related
issues that are possible when running as a service. It is usually simpler
to first try to get things worked out as a console.

Cheers,
Leif



On Thu, Jan 30, 2014 at 11:44 PM, Seamus McMorrow
<sea...@gm...>wrote:

> Hi,
>
> I am evaluating using Tanuki JSW as a wrapper for my java application.
>
> I have created a java application which manages a check scanner through a
> seperate "DeviceManger.exe" application, It is using COM/ActiveX OCX
> control to communicate.
>
> My java application starts the devicemanager.exe with a call like
> Runtime.getRuntime().exec(".....devicemanager.exe"). A dll related to
> devicemanager.exe is wrapped by ezjcom, to communicate events to the
> devicemanager.exe
>
> When I run this application as a standard java application everything
> works fine!
>
> However when I try to run the application with the wrapper from command
> line or as windows service, something isn't quite right, the communication
> between the wrapped java application, and the DeviceManger.exe does not
> seem to be working correctly. It seems as if there is something
> restricting/blocking the DeviceManger.exe. Unfortunately I don't have any
> error message, as this may be deep in the wrapper or windows dlls.
>
> I am using the 32bit version of the latest wrapper, as the dlls require
> this.
>
> I have tried enabling debug logging, java security with all permissions
> allowed. And still nothing seems to be working. I am currently looking at
> registering the OCX controls using regsvr32, etc, but having no luck.
>
> Does anyone have any idea on how I might debug this further or fix this
> issue?
>
> Kind Regards,
> Seamus
>