wood burning stoves*
The moose likes Swing / AWT / SWT and the fly likes Scott:  Deployment Statagies Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Swing / AWT / SWT
Bookmark "Scott:  Deployment Statagies" Watch "Scott:  Deployment Statagies" New topic
Author

Scott: Deployment Statagies

Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15299
    
    6

I was wondering if your book covered in deployment stratagies for rich client applications? Do you think JWS is good enough? How about the JRE version issue?

Thanks.


GenRocket - Experts at Building Test Data
Carol Enderlin
drifter
Ranch Hand

Joined: Oct 10, 2000
Posts: 1364
I'm looking at the Chapter Summaries on the SourceBeat Desktop Java Live page.

Part 2 of the book is Desktop Application Design. The last chapter in that section is

Chapter 10. Application Deployment

An application can only be used if it can be properly installed on your user's machines. Java based deployments have evolved over the years. A number of installation methods are now available. This chapter looks at what each method provides. It also looks at the environment and applications each is best suited for.

  • Applets
  • Java2Exe
  • Java based installers
  • Webstart
  • JNLP Optimizations (supposed to be indented under webstart)


  • Looking forward to Scott's answers.
    [ April 05, 2005: Message edited by: Carol Enderlin ]
    Scott Delap
    author
    Ranch Hand

    Joined: Apr 05, 2005
    Posts: 73
    Actually the book chapters have changed slightly since that TOC was posted:

    1. Reintroducing the Rich Client
    2. Layout Managers
    3. GUI Builders
    4. Look and Feel
    5. Threading
    6. Data Binding
    7. Validation

    8 and maybe 9 will be writing a sample application. Then I'm going to come back in and address deploying the application, GUI Testing, communications, etc.

    Now back to your question. As you can see from the proposed outline, I'm going to break down various installer technologies, Java to exe conversions, applets, and WebStart. The JRE issue as I commented in a response to the other question isn't one that just goes away tomorrow. In corporate deployments you have more room with standard configurations on machines. For a commercial application the only 100% way to know you are running on the desired JRE is to bundle it. This is what Jetbrains does for instance with the Windows version of IDEA. I've seen a few blog posts where people have gotten the JRE down to 7 or 8 megs with compression and removing unneeded classes. That being said it is much more likely to find a machine with a 1.4 JRE than even a year ago. I see that trend of having an up to date JRE on a machine only increasing going forward with Sun's new auto update features built into Java.
    Scott Delap
    author
    Ranch Hand

    Joined: Apr 05, 2005
    Posts: 73
    I just noticed I didn't address JWS specifically. It is getting close. I think the next version of Java will get it very close. If you look at the last webstart chat

    http://java.sun.com/developer/community/chat/JavaLive/2005/jl0301.html

    the new version is targeting ease of deployment. They seem to be addressing the vast majority of developer concerns that are left with Web Start as a deployment technology.
     
    GeeCON Prague 2014
     
    subject: Scott: Deployment Statagies