3.3. Comparison between deployment using Java Web Start and just centralizing the add-ons on a HTTP server
Prev | 3. Deploying XXE using Java™ Web Start | Next

### 3.3. Comparison between deployment using Java Web Start and just centralizing the add-ons on a HTTP server

Deploying XXE using Java™ Web Start | Centralizing add-ons on a HTTP server
--- | ---
XXE code is downloaded and cached on the PC of the XXE user. | XXE code is installed by the XXE installer on the PC of the XXE user.
Spell-checker dictionaries are downloaded and cached on the PC of the XXE user. | Spell-checker dictionaries are installed by the XXE installer on the PC of the XXE user.
Plug-ins are downloaded and cached on the PC of the XXE user. | Plug-ins stay on the server and therefore are not cached on the PC of the XXE user.
By default, configuration files and associated resources (DTD, CSS, icons, etc) are downloaded and cached on the PC of the XXE user. (Use the `-online` option if you prefer to keep configuration files on the deployment server.) | Configuration files and associated resources (DTD, CSS, icons, etc) stay on the server and therefore are not cached on the PC of the XXE user.
User can work offline. | User cannot work offline.
Personal add-ons installed on the user preferences directory of user (that is, ``%APPDATA%`\XMLmind\XMLeditor\addon\` on Windows and ``$HOME`/.xxe/addon/` on Unix) are ignored. | Personal add-ons installed on the user preferences directory of user are loaded.
Upgrading, for example, from XXE v3.9 to XXE v3.10 is automated for the user. | For example, user will have to manually uninstall XXE v3.9 and then to manually download and install XXE v3.10.

Prev | Up | Next
3.2. Deploying XXE using Java™ Web Start, a step by step description | Home | Part II. Reference