jnilib library MIME type

Classic Servoy
1

My plugin uses a JNI library that is in:
/Servoy/plugin/myplugin/libA.jnilib

I have a JNLP file for my plugin with the line:

When I try to access Servoy from a client a get a download error that says the server sent a wrong MIME type for resource:
http://192.168.xxx.xxx:8080/plugin/myplugin/libA.jnilib - null

I think I have to add a MIME type for jnilib to my Apache server, but what is the correct MIME type for jnilib files?

2

I’m on Mac OS X Server 10.4.2.
I tried to set the MIME type “application/octet-stream” to the files with the .jnilib extension editing files “/private/etc/httpd/mime.types” and “/private/etc/httpd/httpd.conf”, but I still get the same error (null MIMe type sent).
Any suggestion?

3

Are you downloading the jni lib from an Apache server or are you accessing it via the Servoy ApplicationServer’s Tomcat instance? Because if you are using Servoy’s Tomcat instance you should modify the web.xml file (which contains all the mime types by extensions).

4

You was right, I was using Servoy’s Tomcat instance but modified Apache server config files.
Now I added the following lines to web.xml:

<mime-mapping>
  <extension>jnilib</extension>
  <mime-type>application/octet-stream</mime-type>
</mime-mapping>

However now I get a different error that says:
Corrupted JAR file in http://192.168.xxx.xxx:8080/plugin/myplugin/libA.jnilib

Should I pack the jni lib in a jar file to distribute it?

5

See:

http://www.vamphq.com/jnlpref/tag-nativelib.html

So the answer is yes, and I guess you don’t need to change web.xml since it already knows the mime type for jars.

6

Thanks a lot, I thinked I could distribute the library unpacked reading Mirona’s JNLP example file in this thread, but I was clearly wrong.
Now it works, but I have one last question: from a client is it possible to see messages sent to standard output and standard error through java methods System.out.println() and System.err.println()?
I tried with Mac OS X application Console but on the client machines I didn’t get any messages in console.log.