The Problem with Java Clients

This is typical of the problems with using Java as a management interface for a network device.

The Management Application (graphical user interface used to configure the Unit’s software) runs as a stand-alone Java Web Start application (tested on Microsoft Windows™ operating system only). The application requires Java Runtime Environment (JRE) 1.6.0_07 or higher, although there are issues with some of the JRE releases. See “Java Runtime Environment Version 6.0 Problems” on page 19 for details

This is a real piece of documentation from a current product. And they seriously expect me to use it ?

You are joking right ?

Hate Java.

  • Daveyk

    Well at least it didn’t say “1.6.0_07 or lower”

  • packeteer

    cisco webvpn makes me loath java

  • Colin

    “But that’s what we learnt to program with in university/college/tertiary-paid-to-much-to-learn-nothing classes so we just used it when someone started paying us money to turn up at an office where we have to wear shoes and pants!”

  • Jother

    “Hate Java”

    It’s fine for server side stuff but for client side stuff it has been horrible.  Some of the tools work so poorly you wind up with a dedicated machine (VMs these days) … or two … or three … etc.

  • Evan Weston

    Now I’m curious as to what the app is. Name and shame 😀

  • Romans Fomicevs

    is any1 wonders why we are still using good ol’ CLI? tried java thing to manage cisco routers… was deeply impressed by how cisco bad at doing GUI managements.

  • Mark Swanborough

    You want a cross platform GUI? Java: versions and security pain, but pretty fast. Flash: versions, securi *crash*, what was I saying? Oh yeah, security, but *crash* grr, but performance is OK. HTML+JS: browser compatibility issues, performance issues, lack of canvas until recently (SVG plugins not withstanding), browser compatibility is really hard, oh, and performance (it’s not compiled, hard to profile, yada yada yada).

    6 years ago, Java was the best choice of a bad bunch, unless you were willing to invest heavily in JS, and didn’t want any fancy UI (break out to Java applets, flash, or mix in SVG and you’re back in the world of pain).

    • Greg Ferro

      Sure. I want an HTML5 app like whats on my smartphone.

      I want an app that doesn’t need insecure plugins to operate. I want an app that works in web browser to avoid requesting the desktop team to install Java.

      In 2014, HTML5 is the standard. it’s time for the vendors to invest in their front end instead of mistreating their customers. We are already turning other suppliers who make usable, attractive software.

  • danmassa7

    Just had my first experience with the Cisco AIP-SSM (the IPS module for the ASA5500.) The ASA5510 it was in is EoL but the AIP-SSM is a current product. The 7.1(7)E4 software is the current shipping engine. Does not work with Java 1.7.0_65. TAC has tested and supports 1.7.0_45 and they have no workaround for patch 65 except to uninstall 65 and install 1.7.0_45 fresh.
    Bravo [insert slow clapping here.]