Running XMLmind XML Editor as an
generation JavaTM plug-in” can be used to run XMLmind XML
Editor Professional Edition as an applet.
More precisely the requirements for running XMLmind XML
Editor as an applet are:
- A Java runtime version 1.6.0_10 and above.
- A Web browser supporting the next generation Java plug-in.
Linux users: please make sure that your Web
browser is actually using the next generation Java plug-in, and not the
legacy plug-in. In order to check this, please refer to Java Plug-in Configuration .
there is no simple way to run XXE as an applet on Mac OS X.
More information in Known
problems when XMLmind XML Editor runs as an
- The applet must be signed using a digital certificate.
applet, XMLmind XML Editor is periodically tested against the most recent
releases of Internet Explorer, Firefox, Google Chrome, Safari, and this,
always with the most recent release of the Java runtime 1.6+.
given the fast evolving nature of Web browsers and of Java runtimes, we
cannot guarantee that the above requirements are sufficient to successfully
run XXE as an applet. Therefore, we strongly recommend
interested persons to thoroughly test our applet against their specific Web
browser/Java runtime combinations.
This also implies that, for now,
XXE cannot be deployed as an applet in working environments
where the Web browser/Java runtime combination is not strictly controlled.
(This limitation applies only to the applet, not to XXE running
as a desktop application or deployed using Java Web
More information in Known problems when XMLmind XML
Editor runs as an applet.
As an applet, XMLmind XML
Editor is available in four kinds. Each applet kind is designed to solve a
different problem and thus, has a different user interface.
(click to enlarge)
A document viewer having no user interface at all except a
right-click popup menu.
Run demo .
A single document, single view, document editor designed to
be part of an HTML form.
When the form is about to be
the XML source of the document being edited (and also the local
image files possibly inserted in the document by the author). This
XML source is then passed to the back-end (CGI, servlet, etc) by the
means of a hidden form field.
This works because all
XMLmind XML Editor applets have a small set
of methods specially designed to be scripted using
demo . (See requirements.)
Same single document, single view, document editor, as
editor1, except that, unlike editor1, editor2
has a Save button and fully supports Save
editor2 is designed to be integrated with
a server supporting WebDAV, FTP, FTPS or SFTP (in fact, any kind of
storage for which a virtual
drive plug-in is available).
Full XMLmind XML Editor. Same user interface as the desktop
application, except that it has no File|Quit menu
Despite the fact that applet kinds have vastly different user
interfaces, it is still XMLmind XML Editor. That is, all applet kinds
support the same user preferences and the same add-ons as the desktop
XMLmind XML Editor is deployed as an applet using
deploywebstart, the same command-line tool used to deploy it as a
Web Start application. Deploying XXE as an applet is as
simple as running: deploywebstart -applet applet_kind.
Example: deploywebstart -applet editor2. More information in XMLmind XML Editor - Configuration
- User License puts no restrictions on
the deployment of XMLmind XML Editor as an applet, except of course,
that the number of concurrent users must not exceed the total number of
users for which the license fee has been paid.
- Site License restricts the
deployment of XMLmind XML Editor as an applet to machines located at the
site of the licensee.
- Developer License puts no
restrictions whatsoever on the deployment of XMLmind XML Editor and, of
course, this includes the deployment as an applet.
- Applet Server License allows to
freely deploy XMLmind XML Editor as an applet (but only as an applet,
not as a desktop application) provided that the code of the applet is
downloaded from the servers for which the license fee has been