I moving it to sail-dev so it can be archived and get more eyes. That is not the most up-to-date jnlp, this is: http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/authoring-everything-snapshot/authoring-everything-snapshot.jnlp
That jnlp gets updated each time someone builds the "PAS Jnlp Parent" project on the tels continuum: http://www.telscenter.org/continuum/servlet/continuum/ It should have every jar needed to author any of the tels activities. Because it has a href attribute on the <jnlp> element, webstart will go to that url value of that href attribute and look for updates to the file each time it is run. So you either need to remove the href attribute, or you should use one of the timestamped jnlps located here: http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/authoring-everything-snapshot/ For a demo portal bundle you should consider creating your own jnlp webapp (war) which has your own jnlps and jars. It is pretty easy to do. I will make a up a confluence page documenting the process. Basically it is: - setup the WEB-INF folder, - configure a maven property telling it where your webapp is - check out the pas-jnlp project from tels svn, - and run a maven goal. In that case the authoring tool and client will use the same set of jars, all under your control. Updating them to the latest version requires running a maven goal. Scott On Fri, 2007-05-11 at 09:53 -0400, Anthony Perritano wrote: > yes, it will be hard to keep up to date, because when the code is > changed it needs to be re-deployed thus this jnlp gets changed. > > i think every jar is listed. even otrunk and stuff for the models? > > scott is this a correct statement? > > -Tony > > On 5/11/07, Laurel Williams <[EMAIL PROTECTED]> wrote: > > Hi Tony, > > Can I use the jnlp that you have at: > > http://tels-develop.soe.berkeley.edu:8080/maven-jnlp-snapshot/authoring-everything-snapshot.jnlp > > <http://tels-develop.soe.berkeley.edu:8080/maven-jnlp-snapshot/authoring-everything-snapshot.jnlp> > > > as the template for the jnlp we use to launch the portal? I would like > to copy the jnlp file > to the portal and enter it as part of the versioned files as a > resource. > > Will this be a file that will change periodically? often? will it be > hard to keep it up to date? > > I'm assuming that because it is an "authoring-everything-snapshot" > that > it lists practically every jar that would > be needed to author almost any type of PAS curnit containing any type > of > step. Are there restrictions? Is there anything > you think I should know? > > Laurel > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
