MarvinSketch and MarvinView in HTML page

Hi,

I has been a long time, and I forget how to add MarvinSketch (or MarvinView) in HTML page. I can figure out the HTML codes for the applet through your examples. But the reason the applet is not working, I believe, is the .jar files on the Tomcat server. What .jar files I must include on the server (for a Java web application). I tried jmarvin.jar and appletlauncher.jar, and seems not working. Please help and thanks.

Ben Li 

Please see this example for the Marvin Sketch applet:

MarvinSketch Example - Embedding MarvinSketch applet in HTML pages

and this one for Marvin View:

MarvinView Example - Embedding MarvinView applet in HTML pages

You can find detailed description in above examples how to embed Marvin Sketch / View applets into an HTML page.

You need all jars and other binaries for the applet. Please also read the linking forum topic that describes which resources you need to run the applet:

required files to run Marvin applets

 

Following jar files should not be modified because they are signed jars. If you do so, the modified jar is no longer signed.

 

1. Download and unpack marvin-bin-5.0.0alpha12.tar.gz or marvin-bin-5.0.0alpha12.zip.


2. Create a new directory: marvintmp


3. Unzip jmarvin.jar and every jar file from sjars directory and its subdirectories to the new directory:

	    unzip -o jmarvin.jar -d marvintmp

	    unzip -o sjars/abbrevgroupexport.jar -d marvintmp

	    unzip -o sjars/batik-core.jar -d marvintmp

	    unzip -o sjars/clean2d.jar -d marvintmp

	    ...

	    

 

 

 

Change location to the new directory and create a new jar file:

	    cd marvintmp

	    zip jmarvin.jar *

	    

Wedding Hairstyles

The text that you have attached about jar merging from the Marvin Applets FAQ is already deprecated. Because of it, I have removed the deprecated section from the Marvin Applets FAQ.

 

Modifying of jar files in Marvin Applets package are strongly NOT recommended because of the following reasons:

• Marvin Applets runs only in signed context. If jar files are repacked/rebuilt, they are not signed anymore.


• The core jar includes only essential binaries. Required modules are (down)loaded on demand (to reduce startup time).  If you merge everything into a big jar, the startup performance will decrease significently because most of jars are not needed by startup.


• If you want to preload frequently used modules, you can do it with applet parameter. It is a more effective way for fast access these modules than merge them manually into the core one.


• If you repack jar files, upgrade to a new version will be more complicated.

If you have any problem with loading of the applets please give a detailed description about it. I do not believe that repacking of jar files would be the best solution.