Using JOGL in Java Web Start - Revision history

Sgothel: /* Testing your program outside JWS */ use the native jar lib loading mech, no hassle to deal w/ native libs manually

2012-08-20T23:03:47Z

Testing your program outside JWS: use the native jar lib loading mech, no hassle to deal w/ native libs manually

← Older revision		Revision as of 01:03, 21 August 2012
Line 171:		Line 171:
	= Testing your program outside JWS =		= Testing your program outside JWS =

	It's probably a good idea to test your program outside JWS first, to make sure it does what you think it should. To do that, you'll need to unzip the native binaries so Java can see them. Since I ran first on Windows 7 64-bit, I unzipped all the <tt>*-natives-windows-amd64.jar</tt> files, the collected the DLLs inside into a directory called <tt>lib-windows-amd64</tt>. Since I test on the other platforms too, I did the same for the other four platforms, creating four more directories <tt>lib-windows-i586</tt>, <tt>lib-linux-i586</tt>, <tt>lib-linux-amd64</tt>, and <tt>lib-macosx-universal</tt>.		It's probably a good idea to test your program outside JWS first, to make sure it does what you think it should.

	~~Then to test your program on 64-bit Windows~~, cd to ~~your application directory and type~~		We utilize the [{{SERVER}}/jogl/doc/userguide/index.html#automatednativelibraryloading automated native library loading mechanism], hence we do not bother to hassle with the native libraries ourselves.

	~~<pre>~~		Then to test your program, cd to your application directory and type
	~~java -classpath "gluegen-rt.jar;jogl-all.jar;onetriangle.jar" -Djava.library.path=lib-windows-amd64 name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT~~
	~~</pre>~~

	~~On 64-bit Linux, type~~

	~~<pre>~~
	~~java -classpath "gluegen-rt.jar:jogl-all.jar:onetriangle.jar" -Djava.library.path=lib-linux-amd64 name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT~~
	~~</pre>~~

	~~On Mac OS X~~, type

	<pre>		<pre>
	java -classpath "gluegen-rt.jar:jogl-all.jar:onetriangle.jar" ~~-Djava.library.path=lib-macosx-universal~~ name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT		java -classpath "gluegen-rt.jar;jogl-all.jar;onetriangle.jar" name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT
	</pre>		</pre>

Sgothel: jogl.all.jar -> jogl-all.jar (rc10)

2012-08-20T22:53:56Z

jogl.all.jar -> jogl-all.jar (rc10)

← Older revision		Revision as of 00:53, 21 August 2012
Line 67:		Line 67:
	*/		*/
	public class OneTriangleAWT {		public class OneTriangleAWT {

	~~static {~~
	~~// setting this true causes window events not to get sent on Linux if you run from inside Eclipse~~
	~~GLProfile.initSingleton( false );~~
	}

	public static void main( String [] args ) {		public static void main( String [] args ) {
Line 134:		Line 129:
	<pre>		<pre>
	gluegen-rt.jar		gluegen-rt.jar
	jogl.all.jar		jogl-all.jar

	gluegen-rt-natives-windows-i586.jar		gluegen-rt-natives-windows-i586.jar
Line 159:		Line 154:

	<pre>		<pre>
	javac -classpath "gluegen-rt.jar;jogl.all.jar" name\wadewalker\jogl2tests\onetriangle\*.java		javac -classpath "gluegen-rt.jar;jogl-all.jar" name\wadewalker\jogl2tests\onetriangle\*.java
	</pre>		</pre>

Line 165:		Line 160:

	<pre>		<pre>
	javac -classpath "gluegen-rt.jar:jogl.all.jar" name\wadewalker\jogl2tests\onetriangle\*.java		javac -classpath "gluegen-rt.jar:jogl-all.jar" name\wadewalker\jogl2tests\onetriangle\*.java
	</pre>		</pre>

Line 181:		Line 176:

	<pre>		<pre>
	java -classpath "gluegen-rt.jar;jogl.all.jar;onetriangle.jar" -Djava.library.path=lib-windows-amd64 name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT		java -classpath "gluegen-rt.jar;jogl-all.jar;onetriangle.jar" -Djava.library.path=lib-windows-amd64 name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT
	</pre>		</pre>

Line 187:		Line 182:

	<pre>		<pre>
	java -classpath "gluegen-rt.jar:jogl.all.jar:onetriangle.jar" -Djava.library.path=lib-linux-amd64 name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT		java -classpath "gluegen-rt.jar:jogl-all.jar:onetriangle.jar" -Djava.library.path=lib-linux-amd64 name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT
	</pre>		</pre>

Line 193:		Line 188:

	<pre>		<pre>
	java -classpath "gluegen-rt.jar:jogl.all.jar:onetriangle.jar" -Djava.library.path=lib-macosx-universal name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT		java -classpath "gluegen-rt.jar:jogl-all.jar:onetriangle.jar" -Djava.library.path=lib-macosx-universal name.wadewalker.jogl2tests.onetriangle.OneTriangleAWT
	</pre>		</pre>

Line 296:		Line 291:
	<resources>		<resources>
	<jar href="gluegen-rt.jar" />		<jar href="gluegen-rt.jar" />
	<jar href="jogl.all.jar" />		<jar href="jogl-all.jar" />
	</resources>		</resources>

Line 356:		Line 351:
	<pre>		<pre>
	jarsigner -keystore testKeys gluegen-rt.jar ww		jarsigner -keystore testKeys gluegen-rt.jar ww
	jarsigner -keystore testKeys jogl.all.jar ww		jarsigner -keystore testKeys jogl-all.jar ww

	jarsigner -keystore testKeys gluegen-rt-natives-windows-i586.jar ww		jarsigner -keystore testKeys gluegen-rt-natives-windows-i586.jar ww

Wwalker: Explained differences between hosted and local JARs more clearly

2012-04-19T17:03:21Z

Explained differences between hosted and local JARs more clearly

← Older revision		Revision as of 19:03, 19 April 2012
Line 202:		Line 202:
	= Writing the JNLP files =		= Writing the JNLP files =

	Read the JWS [http://download.oracle.com/javase/1,5.0/docs/guide/javaws/developersguide/syntax.html Java Network Launching Protocol (JNLP)] specification for details.		In general we will have one JNLP file for each JWS application, which will reference the JOGL extension's JNLP file.
			The latter may reference even more JNLP files, but this does not matter in this discussion. Read the JWS [http://download.oracle.com/javase/1,5.0/docs/guide/javaws/developersguide/syntax.html Java Network Launching Protocol (JNLP)] specification for details of the JNLP syntax.

	~~In general we will have one exclusive JNLP file for each application, which will reference the JOGL extension~~'s ~~JNLP file.~~		== Option 1: Use JogAmp's hosted JAR and JNLP files ==
	~~The latter may reference even more~~ JNLP files~~, but this shall not matter in this discussion.~~

	~~== Use~~ JogAmp's ~~deployed~~ files ==		If you're using JogAmp's hosted JAR and JNLP files, you only have to write your application's JNLP file, since it will reference JogAmp's official release as an extension.

	We only have to write ~~our~~ application's JNLP file, since it will reference JogAmp's official ~~released~~ as an extension.

	<pre>		<pre>
Line 240:		Line 238:
	Save this file to your application directory as <tt>OneTriangleWebStart.jnlp</tt>.		Save this file to your application directory as <tt>OneTriangleWebStart.jnlp</tt>.

	If you ~~decide to use our~~ JogAmp ~~signed Jar and Jnlp~~ files you can skip the next chapter.		If you are using JogAmp's hosted files you can skip the next chapter.

	== Use ~~your own~~ JogAmp files ==		== Option 2: Use local copies of the JogAmp JAR files ==

	Here we have to write ~~the~~ JNLP file for our application and ~~once~~ for our self deployed JogAmp extension.		Here we have to write one JNLP file for our application and one for our self-deployed JogAmp extension.

	<pre>		<pre>
Line 346:		Line 344:
	Note that the <tt>codebase</tt> values are set to the current working directory, and the <tt>href</tt> values are simple filenames. This is so we can test the JNLP app locally, without using a web server. When we put the app on a web server later, the <tt>codebase</tt> and <tt>href</tt> become full URLs.		Note that the <tt>codebase</tt> values are set to the current working directory, and the <tt>href</tt> values are simple filenames. This is so we can test the JNLP app locally, without using a web server. When we put the app on a web server later, the <tt>codebase</tt> and <tt>href</tt> become full URLs.

	=== Signing your JARs ===		=== Signing your local copies of the JogAmp JARs ===

	For the JWS app to work properly in a web browser, all its JARs must be signed with the same key. Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.		For the JWS app to work properly in a web browser, all its JARs must be signed with the same key. Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.

Wwalker: Removed nativewindow and newt JARs from command lines

2012-04-19T16:53:54Z

Removed nativewindow and newt JARs from command lines

← Older revision		Revision as of 18:53, 19 April 2012
Line 159:		Line 159:

	<pre>		<pre>
	javac -classpath "gluegen-rt~~.jar;nativewindow.all~~.jar;jogl~~.all.jar;newt~~.all.jar" name\wadewalker\jogl2tests\onetriangle\*.java		javac -classpath "gluegen-rt.jar;jogl.all.jar" name\wadewalker\jogl2tests\onetriangle\*.java
	</pre>		</pre>

Line 165:		Line 165:

	<pre>		<pre>
	javac -classpath "gluegen-rt~~.jar:nativewindow.all~~.jar:jogl~~.all.jar:newt~~.all.jar" name\wadewalker\jogl2tests\onetriangle\*.java		javac -classpath "gluegen-rt.jar:jogl.all.jar" name\wadewalker\jogl2tests\onetriangle\*.java
	</pre>		</pre>

Wwalker: Augmented explanation of local vs. hosted JAR files

2012-04-19T16:51:52Z

Augmented explanation of local vs. hosted JAR files

← Older revision		Revision as of 18:51, 19 April 2012
Line 121:		Line 121:
	* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.		* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.

	== ~~Using your own signed~~ JogAmp JAR files (optional) ==		== Get local copies of the JogAmp JAR files (optional) ==

	A Java Web Start app can either use its own local copies of the [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs GlueGen] ~~and~~ [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs JOGL] JAR files, or it can use the copies hosted at jogamp.org. To ~~use~~ local JAR files, do this:		A Java Web Start app can either use its own local copies of the [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs GlueGen], [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs JOGL], and native JAR files, or it can use the copies hosted at jogamp.org.

			Using local copies of the JogAmp JAR files gives you complete control over which version of JOGL your app uses, and guarantees that version will never change unexpectedly. However, it does require more work on your part to install and sign the JARs, and it increases the load on your server.

			To get local copies of the JogAmp JAR files, do this:

	* Read [[Downloading_and_installing_JOGL]] for instructions on how to get the autobuild or released JAR files.		* Read [[Downloading_and_installing_JOGL]] for instructions on how to get the autobuild or released JAR files.

Wwalker: Moved mention of which JARs must be signed into the signing section

2012-04-19T15:48:15Z

Moved mention of which JARs must be signed into the signing section

← Older revision		Revision as of 17:48, 19 April 2012
Line 120:		Line 120:
	* Create a subdirectory <tt>name/wadewalker/jogl2tests/onetriangle</tt> inside your application directory. Or if you changed the packages of the files above, create a subdirectory that matches your package names.		* Create a subdirectory <tt>name/wadewalker/jogl2tests/onetriangle</tt> inside your application directory. Or if you changed the packages of the files above, create a subdirectory that matches your package names.
	* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.		* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.

	~~Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.~~

	== Using your own signed JogAmp JAR files (optional) ==		== Using your own signed JogAmp JAR files (optional) ==
Line 346:		Line 344:
	=== Signing your JARs ===		=== Signing your JARs ===

	For the JWS app to work properly in a web browser, all its JARs must be signed with the same key. If you don't already have a key you want to use, you can create one like this		For the JWS app to work properly in a web browser, all its JARs must be signed with the same key. Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.

			If you don't already have a key you want to use, you can create one like this

	<tt>keytool -genkey -keystore testKeys -alias ww</tt>		<tt>keytool -genkey -keystore testKeys -alias ww</tt>

Wwalker: Added explanation of self-hosted vs. JogAmp-hosted JAR files

2012-04-19T15:46:30Z

Added explanation of self-hosted vs. JogAmp-hosted JAR files

← Older revision		Revision as of 17:46, 19 April 2012
Line 116:		Line 116:

	= Setting up the application directory =		= Setting up the application directory =

	~~Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.~~

	* Create a directory to hold your JWS application.		* Create a directory to hold your JWS application.
Line 123:		Line 121:
	* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.		* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.

	~~If you decide~~ to ~~use~~ the signed JAR ~~and JNLP~~ files ~~hosted by JogAmp you can skip the next chapter.~~		Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.

			== Using your own signed JogAmp JAR files (optional) ==

	~~== Using your~~ own ~~signed JAR and JNLP files ==~~		A Java Web Start app can either use its own local copies of the [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs GlueGen] and [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs JOGL] JAR files, or it can use the copies hosted at jogamp.org. To use local JAR files, do this:
	* Copy all JogAmp JAR files (both [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs GlueGen] and [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs JOGL]~~) into the application directory.~~
	** Read [[Downloading_and_installing_JOGL]] for instructions on how to get the autobuild or released JAR ~~and JNLP~~ files.
	* Copy the JogAmp [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.~~html#JNLPFiles JNLP~~ files~~] into that application directory~~

	~~Here's a list of~~ the files ~~you should copy~~:		* Read [[Downloading_and_installing_JOGL]] for instructions on how to get the autobuild or released JAR files.
			* Copy the following JAR files into the application directory:

	<pre>		<pre>

Wwalker: Fixed links href text

2012-04-19T15:39:05Z

Fixed links href text

← Older revision		Revision as of 17:39, 19 April 2012
Line 126:		Line 126:

	== Using your own signed JAR and JNLP files ==		== Using your own signed JAR and JNLP files ==
	* Copy all JogAmp JAR files ([[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs\|GlueGen]] and [[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs\|JOGL]]) into the application directory.		* Copy all JogAmp JAR files (both [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs GlueGen] and [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs JOGL]) into the application directory.
	** Read [[Downloading_and_installing_JOGL]] for ~~getting~~ the autobuild or released JAR and JNLP files		** Read [[Downloading_and_installing_JOGL]] for instructions on how to get the autobuild or released JAR and JNLP files.
	* Copy the JogAmp [[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JNLPFiles\|JNLP files]] into that application directory		* Copy the JogAmp [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JNLPFiles JNLP files] into that application directory

			Here's a list of the files you should copy:

	<pre>		<pre>

Wwalker: Fixed caps

2012-04-19T15:28:30Z

Fixed caps

← Older revision		Revision as of 17:28, 19 April 2012
Line 117:		Line 117:
	= Setting up the application directory =		= Setting up the application directory =

	Note that none of your applet ~~Jar~~ files needs to be signed. Only the ~~Jogamp~~ files (GlueGen, JOGL, ..) require code signing.		Note that none of your applet JAR files needs to be signed. Only the JogAmp files (GlueGen, JOGL, et cetera) require code signing.

	* Create a directory to hold your JWS application.		* Create a directory to hold your JWS application.
Line 123:		Line 123:
	* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.		* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.

	If you decide to use ~~our JogAmp~~ signed ~~Jar~~ and ~~Jnlp~~ files you can skip the next chapter.		If you decide to use the signed JAR and JNLP files hosted by JogAmp you can skip the next chapter.

	== Using ~~Your~~ own ~~Signed Jar~~ and ~~Jnlp Files~~ ==		== Using your own signed JAR and JNLP files ==
	* Copy all JogAmp ~~Jar~~ files ([[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs\|GlueGen]] and [[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs\|JOGL]]) into the application directory.		* Copy all JogAmp JAR files ([[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#GluegenJARs\|GlueGen]] and [[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JOGLAllInOneJARs\|JOGL]]) into the application directory.
	** Read [[Downloading_and_installing_JOGL]] for getting the autobuild or released JAR and JNLP files		** Read [[Downloading_and_installing_JOGL]] for getting the autobuild or released JAR and JNLP files
	* Copy the JogAmp [[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JNLPFiles\|~~Jnlp~~ files]] into that application directory		* Copy the JogAmp [[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#JNLPFiles\|JNLP files]] into that application directory

	<pre>		<pre>

Sgothel at 15:34, 22 September 2011

2011-09-22T15:34:21Z

← Older revision		Revision as of 17:34, 22 September 2011
Line 122:		Line 122:
	* Create a subdirectory <tt>name/wadewalker/jogl2tests/onetriangle</tt> inside your application directory. Or if you changed the packages of the files above, create a subdirectory that matches your package names.		* Create a subdirectory <tt>name/wadewalker/jogl2tests/onetriangle</tt> inside your application directory. Or if you changed the packages of the files above, create a subdirectory that matches your package names.
	* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.		* Put your <tt>OneTriangle.java</tt> and <tt>OneTriangleAWT.java</tt> files inside the subdirectory.

			If you decide to use our JogAmp signed Jar and Jnlp files you can skip the next chapter.

	== Using Your own Signed Jar and Jnlp Files ==		== Using Your own Signed Jar and Jnlp Files ==
Line 235:		Line 237:

	Save this file to your application directory as <tt>OneTriangleWebStart.jnlp</tt>.		Save this file to your application directory as <tt>OneTriangleWebStart.jnlp</tt>.

			If you decide to use our JogAmp signed Jar and Jnlp files you can skip the next chapter.

	== Use your own JogAmp files ==		== Use your own JogAmp files ==