Recent changes to patches

#4 Ability for third party to instantiate Native process

2013-04-27T11:46:23.312000Z

Your workaround makes sense perfect sense, and I am glad you found a solution.

Thanks a lot for sharing this information!

#4 Ability for third party to instantiate Native process

2013-04-23T07:53:03.063000Z

Thanks for your reply.

Exelsior JET uses a custom java runtime, but I am not so sure about the “magic” behind Excelsior JET. Mainly because of the NoClassDefFoundError exception I think it could be a path problem since some of the paths contain spaces. I tried many different ways to add quotes to the paths, but still didn’t get it to work.

I did however find a way around the spawning problem. In the compilation process it is possible to enable the “Multi-app executable”-feature. This feature creates an executable that can have multiple entry points and you can specify the desired main class to run using arguments. So from my implementation of PeerVMProcessFactory I simply execute my exe-file a second time with arguments matching the NativeInterface main class:
Runtime.getRuntime().exec(“test.exe chrriis.dj.nativeswing.swtimpl.NativeInterface 1 60851”);

I guess this way Excelsior JET calls the main class with the appropriate paths. It’s probably not the most elegant solution, but it works without the inProcess setting which is my primary concern. A drawback is the fact that the name of the exe-file is hardcoded in my code, but I can live with that for now. Everything seems to work right now, but I will continue testing just to make sure and hope I don't find any further drawbacks.

I hope this information helps if anyone else is experiencing similar problems with instantiating the native process using Excelsior JET.

#4 Ability for third party to instantiate Native process

2013-04-19T15:42:21.923000Z

Hi,

To spawn the VM, I need to use the same version of Java. When the process is turned to an exe using Excelsior JET, I am not sure how one would start the VM with a different main class. Where is the VM and where are the runtime libraries when using Excelsior JET?

An alternative would be to ship the JRE and provide an exe for your JAR files (like WinRun4J).

-Christopher

#4 Ability for third party to instantiate Native process

2013-04-15T11:51:09.264000Z

Hello and thanks for a great library!

I realize that there’s been no activity here for a while, but I’ll post anyway and hope you can help me.

As mentioned above the external process created via the command “java“ does not work when compiling to binary using Excelsior JET. On my machine it seems like the VM on the native side is never spawned and I get a "Failed to connect to spawned VM!" exception. But before that three identical exceptions are thrown when trying to create the external process: “Exception in thread "main" java.lang.NoClassDefFoundError: Files/Common”. Maybe just a path problem?

It does however work perfectly if I set the property nativeswing.interface.inProcess=true. I guess this is because using this setting a second VM is never spawned. But using this setting for purposes other than debugging are as far as I can tell discouraged since the native side can crash the entire program at any moment.

I have created a class that implements PeerVMProcessFactory that gets called to spawn the second VM. But have so far been unable to create the external process in a way that Excelsior Jet will accept.

Any feedback or suggestions are greatly appreciated!

2012-09-23T20:16:43.304000Z

2012-09-23T20:16:43.197000Z

2012-09-23T20:16:37.888000Z

2012-09-23T20:16:32.721000Z