Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Pros and cons of javawebstart

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi all

I am about to deploy an SWT application through java webstart.
I have been doing quite a lot of reading on java webstart and i decided
to go for it , for the reason that it allows me to update the client
application from the webserver and all client machines will automatically updated.

Thats some feature. But before i get into getting the whole stuff done,
want to know the disadvantages of using webstart and what am i losing by using webstart.

Now why does the jar needs to be signed for usage thru javawebstart,
whats the significance
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Thats some feature. But before i get into getting the whole stuff done, want to know the disadvantages of using webstart and what am i losing by using webstart.



The standard does not allow passing command line arguments to your java app directly from the URI (URL) used to launch the webstart app.

The command line arguments passed to the application comes from the JNLP descriptor file (XML) located on the server.

The only way I found to pass command line arguments parsed from the URI (URL) is to write a servlet that intercepts JNLP requests for your app and edits the JNLP descriptor file adding command line args from the URI.

This may not be important to you and your application, but it seems to be a glaring omission in the JNLP specification.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
see http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/javaws.html
-open <arguments>
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic