Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: 1.0-alpha-1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
We need specs for a webstart plugin. Below just some notes taken from mails with Kris Bravo.
From Kris:
--------------
I intend to support multiple jnlp apps in a single web application from
the start. So in your case, 2 jnlp applications would require three
project:
project-jnlp1 -> produces jar
project-jnlp2 -> produces jar
project-webapp -> produces webapp w/ jnlp1 & 2 here:
/WEB-INF/web.xml
/jnlp1.jsp <- returns jnlp file to client with proper context root.
/jnlp2.jsp <- ""
/jnlp/project-jnlp1.jar
/jnlp/project-jnlp2.jar
/jnlp/lib/dep-1.jar
/jnlp/lib/dep-2.jar
/jnlp/lib/...
- The jnlp files would be in the webapp project.
- The jar signing would occur in project-jnlp1 & project-jnlp2.
- Compile and runtime dependencies from project-jnlp* would be copied to
jnlp/lib.
Would that layout suffice?
----------
Questions:
- how should the pom look like
- how to use webstart outside of web apps.
There is a ant task which packs a war archive for deployment of a webstart application. I makes use of pack200 and a servlet which supports version comparision as specified in the webstart specification.
The task is available at http://ant-jnlp-war.sourceforge.net/.
The jnlp download servlet is described here http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/downloadservletguide.html.
I consider supporting pack200 a major goal because cat reduce update sizes by magnitudes.