Java Servlets with Applets, JNI, JOGL, etc...

I included this in the advanced section because my question deals with interfacing a lot of things together. It could have gone under Servlets, Applets, 2D/3D, JNI, etc... but it kind of deals with all of these things. I am working on an advanced research project at my University that needs to interface many software tools/parts together. Here is a run down of some of these tools. I will also specify the purpose for each:

Java Servlets with Apache Tomcat --> for a slick GUI (with this I get access to all the web programming tools, css, javascript, ajax, etc..) and to deploy it online.

c programming langauge --> I am doing some very deeply engrained computational things (numerical analysis, fitting, complicated math) where the complex functions are written in c.

JNI (Java Native Interface) --> I need this to call c from my GUI interface.

Applets --> I need to have interactive programs on the web page to run the c functionality.

JOGLE (Java Open GL) --> Not only do I need Java interactive programs, but I also need to program some graphically intense things.

My problem comes in tieing and interfacing all of these things together. What I want to do for this particular part of the project is have a user navigate with Servlets to a page that loads and runs an applet (which underneath the applet is calling complicated c algorithms using JNI, and feeding the results to JOGLE to get the graphics) (I know someone might ask why not just stick with open GL, but that is out of the question, I am keeping with JOGLE).

My background on everything is:
Servlets, web programming, etc... --> I know inside and out.

JNI --> I am learning it now.

Applets --> I've done many times, but have never embedded in a Servlet program/platform and have never used JOGLE with one.

JOGLE --> I've done some Joggle applications before, but never have interfaced it with a deployable applet.

Now that you understand the task and my background then my question is: Are there any good resources for interfacing these different components that anyone can direct me to? I am not looking for a 1 million page manual to learn all the ins and outs of Jogle or jni, I would rather like suggestions from experienced users on the matter for excellent resources for integrating and interfacing the different parts. Any help would be much appreciated!

Also even if there isn't an all encompasing solution or answer to this problem then I wouldn't mind someone directing in the right direction for the following problems:
--> integrating applets with Java servlets using eclipse and apache tomcat

--> Good way to tie Jogle into a Java applet

--> Interfacing Java Servlets with JNI

If I even had resources for searching out these things then that would help out alot.

Thanks,
Steven Miller:)

If you want to run 3D in a browser, you should probably look at using an engine designed for that rather than JOGL.

There are several Java 3D web engines available today that you can build an applet around:

List of game engines - Wikipedia, the free encyclopedia

Minecraft is built on this one:

Lightweight Java Game Library - Wikipedia, the free encyclopedia

As far as running JNI goes, your applet will have to be a signed applet for the browser to allow it.

Signed Applet Tutorial

Are you suggesting that I start with a graphics engine so that I don't have to start from the ground up or because jogl won't work that well as far as performance and other things? I am just curious.

Also of the four java graphic engines listed on that wiki page, which would you suggest?

Srry to post another thing right on top(I will wait for a reply before posting another), but I have researched what I need to do and I am thinking about using either Jake2 or Jmonkey. Do you know which is a better graphics engine?

I don't know which is better. It really depends on what you're planning to do with it.

As far as running JOGL in a signed applet, it probably works just fine. But the thing is, you already mentioned you're doing some sort of high intensity processing in native code, and know you're wanting 3D. It won't be long before you want sound and a physics engine too. So rather than slowing reinventing a game engine, you might as well start with one.