Command-line tool deployxxe makes it easy:
Deploying XXE using Java™ Web Start. More information in Chapter 8, Deploying XXE using Java™ Web Start.
Embedding an advanced XML editor based on XXE in a third-party application. More information in Part II, “Embedding an advanced XML editor based on XXE in your Java™ application” in .
In order to do this, deployxxe generates a number of files in its output directory. Most of these files are JAR files, the main one being
When XXE is to be deployed using Java Web Start, deployxxe also generates a
xxe.jnlp file and all the generated JAR files are digitally signed.
xxe.jar file generated by deployxxe is large because it contains:
some of the JAR files found in
all the add-ons you need to be in XXE. Stock add-ons such as: document type configurations (DITA, DocBook, XHTML), a spell-checker engine, spell-checker dictionaries, translations of XXE messages, virtual drive plug-ins, image toolkit plug-ins, etc, but also, custom add-ons if needed to.
In order to determine which add-ons are to be added to the generated
xxe.jar, deployxxe uses the same dynamic discovery technique as the desktop application. How the contents of the the two
addon/ directories of XXE is recursively scanned by deployxxe is explained in Section 1, “Dynamic discovery of add-ons”.
However there slight differences between the dynamic discovery technique used by deployxxe and the one used by the desktop application:
deployxxe ignores the "Quick Start Cache", if any.
deployxxe ignores environment variable
deployxxe has an option
-sysaddonsonly, which instructs it to search for add-ons only inside
and not inside