XMLSpear Known Bug List
Ref B-01
Type Bug/Limitation
Status Open
Affects Version All versions
Fixed in version None
Date Logged 06 Nov 2007
Short Description Entity references in attributes are lost.
Long Description If an xml document is loaded in one of the tree views (treetable view or element view), the entity references used in attributes are replaced by their actual values and the original entity reference is lost. This problem does not effect entity references in elements. This behaviour is caused by a limitation of he Xerces DOM software which does not store the original entity references in the DOM tree.
Workaround The only workaround is to stay in the source view of XMLSpear. But there is currently no way to load an existing XML document directly in the source view. You can open the document from the file tree by right-clicking and choosing "open with". Then open the document with the Simple TextEditor. Select all the text and copy-paste it in an empty source window of the XML editor and stay in this view!
Example In the example xml below, the entity reference in salary="&one; will be lost and will result in salary="1".
The entity reference in <given>&name;</given>is not effected. 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE personnel SYSTEM "personal.dtd" [
<!ENTITY name "Big">
<!ENTITY one "1">
]>
<personnel>

   <person id="Big.Boss" salary="&one;">
      <name>
         <family>Boss</family>
         <given>&name;</given>
      </name>
      <email>chief@foo.com</email>
   </person>
</personnel>
Ref B-02
Type Bug
Status Open
Affects version All versions
Fixed in version None
Date Logged 06 Nov 2007
Short Description XML Schema is changed.
Long Description If an xsd schema which redefines elements, is loaded in one of the tree views (treetable view or element view), it may be modified. This behaviour is caused by a bug in the Xerces schema loader.
Workaround Not available.
Example See this thread in the xerces forum.
Below is the schema which caused the problem.
After loading <xs:extension base="xhtml:head"> is changed in <xs:extension base="xhtml:head_fn3dktizrknc9pi"> 
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema 
    targetNamespace="http://www.w3.org/1999/xhtml"
    xmlns:xs="http://www.w3.org/2001/XMLSchema" 
    xmlns:xsi="http://www.w3.org/1999/XMLSchema/instance"
    xmlns:xhtml="http://www.w3.org/1999/xhtml"
    xmlns:xforms="http://www.w3.org/2002/xforms"
    xsi:schemaLocation=
        "http://www.w3.org/1999/xhtml
             http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd
         http://www.w3.org/2002/xforms
             http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd">

    <xs:redefine 
        schemaLocation="http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd">
        <xs:complexType name="head">
            <xs:complexContent>
                <xs:extension base="xhtml:head">
                    <xs:sequence>
                        <xs:element ref="xforms:model"/>
                    </xs:sequence>
                </xs:extension>
            </xs:complexContent>
        </xs:complexType>
    </xs:redefine>
</xs:schema>
Comment of xerces developer Michael Glavassevich :
The DOM shouldn't have been modified. The schema loader has a bug where it mutates the DOM in order to rename the original component which is being redefined. This was actually fine before JAXP 1.3 came along. Back then the DOM was always built by the schema loader so it didn't matter whether we trashed it. It's not easy to fix. The "xhtml:head_fn3dktizrknc9pi" name should only appear in the XSModel.
Ref B-03
Type Bug
Status Resolved
Affects version 2.42
Fixed in version 2.43
Date Logged 06 Nov 2007
Short Description Creation of new XML document fails with nullpointer exception.
Long Description Creation of new XML document fails with nullpointer exception.
Steps to reprocude.
  • Choose New from the File Menu
  • Choose xml in the document type popup
  • In the Specify Schema popup: Uncheck the "use schema" checkbox and click OK
  • In the Create Root Element popup, leave the element name blank and click OK
In the console you will see the following lines, followed by a java stacktrace 
Create new xml document
Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
Workaround Fill the name of root element in the last (Create Root Element) popup
Example  
Ref B-04
Type Bug
Status Resolved
Affects version 2.4+
Fixed in version 2.43
Date Logged 06 Nov 2007
Short Description Reload document does not work.
Long Description If the opened document is not changed in the editor, the reload document action does not reload the document from the storage. This bug affects the XML and text editor, but does not affect the built-in html viewer.
Workaround If the document is unchanged, which is the case if the floppy icon on the toolbar is disabled, then first make a change in the document before pressing the reload icon. You will be prompted by a popup to confirm the reload.
Example  
Ref B-05
Type Bug
Status Closed
Affects version All versions
Fixed in version  
Date Logged 06 Nov 2007
Short Description Import of MQ message fails with error MQJMS1046: The character set Cp437 is not supported .
Long Description If you import MQSeries messages that come from other platforms, they may contain character sets that are not supported by your java virtual machine. You need to reinstall the java virtual machine (JDK). For old JDK's you have to do a custom install and check the "international support" option. Recent JDK's, for example JDK 6 Update 3, will automatically install the additional language support.
Workaround  
Example  
Ref B-06
Type Bug
Status Closed
Affects version All versions
Fixed in version 2.43
Date Logged 06 Nov 2007
Short Description Display problems with Java Consumer release (Windows) installed. .
Long Description The java SE6 Update N Early Access relaase, also known as java Consumer release or java Family Pack, uses 3D hardware accellaration. There are compatibility issues with some graphic cards, causing all kind of display problems. Please do uninstall the Update N or use the workaround described.
Workaround You can turn of 3D hardware installation by adding the -Dsun.java2d.d3d=false to the java command in the XMLSpear.bat file. Now start XMLSpear from the bat file instead of using the .exe. This workaround is implemented in version 2.43.
Example See this thread in the java forum
Ref B-07
Type Bug
Status Resolved
Affects version 2.42
Fixed in version 2.43
Date Logged 17 Nov 2007
Short Description Reload of XML document fails with nullpointer exception.
Long Description Reload of XML document fails with nullpointer exception.
Steps to reprocude.
  • Open an xml document
  • Switch to source view
  • Make the xml not wellformed and save it.
  • Make another update in the docucument (bug B04)
  • Reload the document
In the console you will see the following lines:
ava.lang.NullPointerException
	at com.donkeydevelopment.eX.a(Unknown Source)
	at com.donkeydevelopment.eX.a(Unknown Source)
	at com.donkeydevelopment.eX.d(Unknown Source)
	at com.donkeydevelopment.eX.a(Unknown Source)
Same as bug B03.
Workaround
Example  
Ref B-08
Type Bug
Status Resolved
Affects version 2.4+
Fixed in version 2.43/td>
Date Logged 17 Nov 2007
Short Description Find jumps to wrong position.
Long Description The find action returns the wrong location. This also results in replacing the wrong text when using the replace functions.
This behaviour occurs in the XML source view for xml documents with CRLF (carriage return,linefeeds). But it only happens in special situations. A known situation is loading an unwellformed xml docucument.
Workaround
Example