The "setup WEB-INF" heading on this page, describes how to setup a JNLPServlet webapp: http://confluence.concord.org/display/CSP/Setup+JNLP+Deployment+Environment
After doing that setup you need to populate the webapp with jar and pack200.gz files. The remainder of the page above explains how to do this using the maven jnlp plugin we've been using. This maven jnlp plugin is a modification of an existing maven jnlp plugin. Getting it to run is not too bad if you are familiar with maven. If you are not familiar with maven it is pretty hard to get it running. If you don't care about size and just want to get something working, you can copy all of the jars and pack200.gz files from an existing jnlpservlet web app. This will be much bigger than you want if you use the main concord or main tels jnlpservlet webapp. So there is another approach which is more simple than getting the maven jnlp plugin to work. And only includes what is needed. It basically takes a jnlp file, parses it and downloads all the resources referenced by it, and saves that jnlp and its resources using the folder and file name structure needed by the JNLPServlet. We made this approach to support the local usb drive server. Privileged users can see more documentation on updating this local usb server here: http://confluence.concord.org/display/UDLP/Updating+UDL+USB+Linux+Server Here is the snippet that is relevant: # make sure you have the correct permissions sudo -u tomcat -i # cd into the jnlp servlet webapp folder cd /web/jnlp_tomcat/webapps/jnlp # download the latest version of java application which does the downloading/updating curl -O http://jnlp.concord.org/dev/org/concord/jnlp2shell/jnlp2shell-1.0-SNAPSHOT.jar # run the JnlpServletCacher class passing in a jnlp url. java -cp jnlp2shell-1.0-SNAPSHOT.jar org.concord.JnlpServletCacher http://jnlp.concord.org/dev/org/concord/maven-jnlp/udl-otrunk/udl-otrunk.jnlp . Here is the generic maven site page for the code which does the downloading and updating: http://source.concord.org/maven2/site/maven2-svn/deploy/jnlp2shell/project-info.html >From there you can get to the source code if you are interested. To use this for PRP you would modify that snippet so it runs the JnlpServletCacher class with the jnlp urls for each jnlp file you want users of the PRP to access. This would probably be the most current jnlps for: - the authoring tool, - pas-learner-runtime plus otrunk. Scott Hiroki Terashima wrote: > Does anybody know what the status of the JNLPServlet is for PRP? A > quick sentence or two or a link to a documentation somewhere that > describes where we are would be helpful. We can talk more about it on > Friday. > > Thanks, > Hiroki > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
