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.
Add-ons of all sorts are downloaded and cached on the PC of the XXE user. (Use the `-online` option if you prefer to keep the add-ons on the deployment server.) | Add-ons of all sorts stay on the server and therefore are not cached on the PC of the XXE user.
User can work offline (unless the `-online` option has been used). | User cannot work offline.
The user cannot install extra add-ons using Options → Install Add-ons. | The user can install extra add-ons using Options → Install Add-ons.
Add-ons found in the user preferences directory of user (that is, ``%APPDATA%`\XMLmind\XMLEditor5\addon\` on Windows and ``$HOME`/.xxe5/addon/` on Linux) are ignored. | Add-ons found in the user preferences directory of user are loaded.
Upgrading, for example, from XXE v4.5 to XXE v4.6 is automated for the user. | For example, user will have to manually uninstall XXE v4.5 and then to manually download and install XXE v4.6.

Prev | Up | Next
3.2. Deploying XXE using Java™ Web Start, a step by step description | Home | 4. Deploying XXE as an applet