from Jogl - User's Guide:
Is it possible to do the same with JInput?
If you publish this jinput.jnlp ...
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
| <?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+" codebase="http://www.newdawnsoftware.com/resources/jinput/webstart/" href="jinput.jnlp">
<information>
<title>JInput</title>
<vendor>New Dawn Software</vendor>
<homepage href="http://jinput.dev.java.net/"/>
<description>JInput</description>
<description kind="short">API for game controller discovery and polled input</description>
<offline-allowed/>
</information>
<security>
<all-permissions/>
</security>
<resources>
<jar href="jinput.jar"/>
</resources>
<resources os="Windows" arch="x86_64 x86">
<nativelib href="jinput-windows-native.jar"/>
</resources>
<resources os="Linux" arch="i386 ia64 x84_64">
<nativelib href="jinput-linux-native.jar"/>
</resources>
<resources os="Mac OS">
<nativelib href="jinput-osx-native.jar"/>
</resources>
<component-desc/>
</jnlp> |
... and sign the jar files with a trusted certificate then everybody can simply insert the following line in the JNLP file:
1
| <extension name="jinput" href="http://www.newdawnsoftware.com/resources/jinput/webstart/jinput.jnlp"/> |
Unsigned applications can still run in the sandbox and the security warning dialog would not appear.
