XMLmind XML Editor V2.9 Patch 1 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml
====================================================
V2.9 Patch 1 (April 4, 2005)
Enhancements:
-------------
* XXE now supports attribute default values as
specified in RELAX NG DTD Compatibility:
http://www.relaxng.org/compatibility-20011203.html
The compatibility of the schema with this
feature is (very strictly) checked by XXE and
not by Jing. This means that a schema found
valid by Jing but improperly using this
feature will be rejected by XXE.
* Changed command xhtml.preview to make it easy
specifying which web browser to use. Example:
add this property element to your
customize.xxe in order to preview XHTML files
using Firefox:
+--------------------------------------------------+
<property
name="XXE_HTML_PREVIEW_COMMAND">"C:\Program Files\Mozilla
Firefox\firefox.exe" "%U"</property>
+--------------------------------------------------+
* User Request: added an invoke element to
process commands. This new element allows to
invoke custom Java[tm] static methods in
process commands. This facility could be used
for example, to zip files in a platform
independent way or to post some files to a web
application.
* Upgraded Norman Walsh's DocBook XSL style
sheets to version 1.68.1.
* The XFC plug-in has been upgraded to XFC V2.1.
Bug fixes:
----------
* Mac only: Alt-key and Shift-Alt-key now work
as expected (for non-dead keys). For example,
with a French keyboard, "Alt-(" generates a
"[" and "Shift-Alt-)" generates a "}".
* Windows only[**]: commands run and start and
process command element shell did not work if
the path to the executable file contained
white spaces, even if this path was properly
quoted.
For example:
+--------------------------------------------------+
<shell
command='"C:\Program Files\Mozilla Firefox\firefox.exe"
"%2"'/>
+--------------------------------------------------+
did not work.
The workaround was to add extra quotation marks
around the command line:
+--------------------------------------------------+
<shell
command='""C:\Program Files\Mozilla Firefox\firefox.exe"
"%2""'/>
+--------------------------------------------------+
This workaround is no longer needed.
* The node path bar did not underline in orange
or in red the elements in non-validating mode.
This bug did not occur when using Java[tm] 1.5,
only when using Java[tm] 1.4.
* Fixed a NullPointerException that happened in
certain conditions when command insertNode was
used to insert a text node.
* Changes made in V2.8 Patch 1 to allow
publishing documents on a WebDAV server using
HTTPS have been removed.
This code was not needed: for HTTPS
connections to work in any Java[tm]
application, the certificate sent by the
secure web site must have been signed by a
Certificate Authority trusted by Java[tm]
(VeriSign, Thawte, Entrust, etc).
When the secure web site sends a certificate
that has not been signed by a trusted
Certificate Authority, you get the following
errors:
+ "Cannot open file "https://XXX/YYY":
sun.security.validator.ValidatorException
: PKIX path building failed:
sun.security.provider.certpath.SunCertPat
hBuilderException: unable to find valid
certification path to requested target";
+ OR "Cannot connect to server
https://XXX/:
peer not authenticated".
In real life, secure web sites almost always
send certificates signed by a Certificate
Authority trusted by Java[tm]. This is of
course not the case for demo/test
certificates. In the latter case, adding a
Certificate Authority to the list known by
Java[tm] is easy:
+--------------------------------------------------+
/# cd $JAVA_HOME/jre/lib/security
/opt/java/jre/lib/security# ls cacerts
cacerts
/opt/java/jre/lib/security# /opt/java/bin/keytool \
-import -alias pixware -file /tmp/pixware.pem \
-keystore cacerts -storepass changeit
/opt/java/jre/lib/security# /opt/java/bin/keytool \
-list -keystore cacerts -storepass changeit
+--------------------------------------------------+
* W3C XML Schema only: the blockDefault and
finalDefault attributes were applied not only
to the direct descendants of a schema element
but also to components obtained from imported
schemas.
Possible incompatibilities:
---------------------------
* Extra quotation marks added to workaround this
bug[**] must now be removed.
* In configuration element include, attribute
system is no longer supported. For example,
replace:
Example:
+--------------------------------------------------+
<cfg:include location="docbook/docbook.xxe"
system="true"/>
+--------------------------------------------------+
must now be replaced by:
+--------------------------------------------------+
<cfg:include location="xxe-config:docbook/docbook.xxe"/>
+--------------------------------------------------+
* Configuration element localize is now ignored.
It has been replaced by configuration element
translation.
