ESYAE-imza Kütüphaneleri

As mentioned in Applet Design the applet mainly consists of two parts one of which is the server code to be used for applet communication. You can think of this server as the system to be logged in.

First of all, you have to deploy the codes in a server which can interpret JAVA and call the page main.jsp. main.jsp , as understood from the code, loads the applet.

In order for this page to load the applet properly the jar file of the applet must be placed in the correct place. You can specify the address of the jar file in the applet tag in main.jsp.

< applet name="webloginapplet" code="tr.gov.tubitak.uekae.applet.light.LightApplet"
	archive=
		"new-applet.jar,

		lib/ma3api-common-1.4.16-20130709.210842-133.jar,
		lib/ma3api-smartcard-1.4.16-20130709.213650-136.jar,

		lib/slf4j-api-1.6.6.jar,
		lib/slf4j-log4j12-1.6.6.jar,
		lib/log4j-1.2.17.jar, a.jar"

	width="0" height="0" MAYSCRIPT>
</ applet>

In the tag above, which loads PKCS 7 signature applet, the main class of the applet is specified as tr.gov.tubitak.uekae.applet.light.LightApplet in the parameter code. It is required that this class must be placed in the jars given in the parameter archive. In our example this class is in new-applet.jar. The address of the jars can be specified by the parameter codebase. If this parameter does not exist then main.jsp will search the applet in its own folder.

Note: Modifying the applet and specifyinh a new jar sometimes may be problematic. The browser may load the old applet from cache. To prevent this, renaming the applet to a different name is suggested.