I just watched an end user of our new app try to get the Java 1.3.1 plug-in installed. The installation process crashed her computer. The plug-in refused to install or run in Netscape 4.78, and only worked in IE. I was hoping the plug-in situation would improve with the next release, since it doesn't seem to easy enough for the end user now. I'll be interested to hear if JWS installation goes easier, and truly works across all browsers (it should, since this time it just launches the app from the browser).
Our app passes serialized objects across the network. Bewilderingly, users who have the 1.3.0 plug-in installed are not prompted to re-install the plug-in (the Swing GUI starts up fine) but they cannot instantiate the objects! I'm still trying to figure out what changed between the 1.3.0 and 1.3.1 plug-ins. If the initial JWS installation is easy enough, it may be the way to go. James Brundege ----- Original Message ----- From: "Farwell, Paul" <[EMAIL PROTECTED]> To: "'Frank D. Greco '" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 5:57 PM Subject: RE: Swing deployment options > You are probably correct. I am overstating the case by saying that Sun might > drop support for the plugin. After XP, it will be the only way to run > applets. (Netscape 6 has also switched to the plugin). But in the long term, > I don't see good reasons to choose the plugin over JNLP. Applets have better > browser support (mainly, a beefier implementation of showDocument() and a > java-to-javascript library) than JNLP, but that's only because Sun has > intentionally limited JNLP-to-browser communication. If Web Start (or JNLP) > supplied a better browser communication API, there would be almost no reason > to use the plugin. > > Just my 2 cents... > _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing
