We Keep Coding

SoapUI: how to include Java file (not Jar file) from external file

similar to "SoapUI: How to include Groovy script from an external file"
how can I import/include .java files in groovy step (not .jar file). The reason we want this is because if we create .jar and loose code somehow, any updates are very much problematic.
Thanks in advance.
using open source version of soapui

Since Java is 99% source compatible with Groovy, you could just rename your .java files to .groovy and the follow the instructions from your linked post.

Use a DLL generated by IKVM

I have generated a DLL froma JAR file using IKVM doing:
ikvmc -target:library mylib.jar
I would like to use the DLL in a Visual C++ project. What are the steps required to call dll functions from my own code? How do I know which methods are exported by the DLL and how do I call them without a header file?

The IKVM.NET is written for the .NET framework 2.0. The usage inside a Visual Studio C++ project can be difficult. But it should be possible to access it via COM interface. Take a look at this answer.

Is there a way to include native libraries in a JAR, like in Java Webstart, without using Webstart?

I'm working on a game that uses LWJGL and thus requires native libraries specific to each platform. On this page, the author shows how to use the <nativelib> tag with Java Webstart to include JARs containing the appropriate native libraries. I'm trying to do something similar, but without using Webstart.
I tried adding the native library JARs to my main executable JAR's classpath, but that didn't work. Currently, the native libraries just sit in the same directory as the main JAR and that works fine, but I'd like to make it a bit tidier.

You have to use the JVM argument -Djava.library.path=/path/to/libs

Generate your jar, then add a script containing something like the following:
#!/bin/bash
java -Djava.libraray.path=. -jar your.jar
Asserting that the native libs are placed in the same folder as your application jar file.

Taking an eclipse java project and packing it into a jar?

Right now i've written a simple SWT application using eclipse, and I want to pack it into an executable .jar file so I can give it out to friends and such. But I have the following problems:
-Right now i'm reading files by using their filename in the program, and putting them in the root folder of the eclipse project. That works fine for running in eclipse, but when I export to jar they're not in the jar. Is there a way to put them in the jar and access them in the code?
-I also need the SWT .jar dependencies or whatever its called(the files you need for SWT).
Does anyone know how to do this?

Take a look at ClassLoader.getResourceAsStream() API.

All you need to do is include these files in the with the source code of your project, then to have access to then have a look at this link

How can I include platform-specific native libraries in the .JAR file using Eclipse?

I am just starting to learn JNI. I have been following a simple example, and I have created a Java app that calls a Hello World method in a native library. I'd like to target Win32 and Linux x86.
My library resides in a DLL, and I can call it just fine using LoadLibrary when the DLL is added to the root of my Eclipse project.
However, I can't figure out how to get Eclipse to export a runnable JAR that includes the DLL and the .SO file for Linux.
So my question is basically; how would you go about creating a project in Eclipse and include several versions of the same native library?
Thank you,
Martin

For runnable JARs, what you need to do is extract to the temporary directory (maybe in a static { } block) and then load the DLL from that directory (using System.loadLibrary() in the same block). To do this, you need to subclass ClassLoader and override the findLibrary() method to allow libraries to be found in that directory. You can do whatever logic you need to here to load the particular platform libraries. To be honest, the naming for the libraries on the different platforms should be similar anyway -- I believe that you omit the 'lib' part when loading, and the extension. That's the gist of it. Probably easier to use One-JAR as the other poster mentioned :)

You might want to check out the One-JAR project. It lets you package your application and its dependencies (including native libraries) to a single jar file.