Release Notes

What's new in XSD 1.1.1? 

  1. Build 20030819_0612SL: Bug Fixes and Improvements
  2. There are numerous bug fixes and improvements included with this build, the most significant of which is described below.

    • The org.eclipse.emf.common.util.URI.java class has been updated to handle resolution of JAR-scheme URIs. Also, comparison of schemes has been made case-insensitive in all URI operations, including testing equality.

  3. Build 20030909_1427WL: Bug Fixes and Improvements
  4. There are bug fixes and improvements included with this build, some of which are described below. Where the description is for a bug reported through Bugzilla, the Bugzilla number is included after the description.

    • 0 and 1 are now accepted as valid boolean XML Schema literals. (Bugzilla 41898)
    • The MagicXMLSchema.xsd, XMLSchema.xsd files in the 1999 and 2000\10 sub-directories of the plugins\org.eclipse.xsd_1.1.1\cache\www.w3.org directory have been updated to fix a problem with old namespace schemas; xml.xsd files, with corresponding old namespace names, have been added to those directories as well. (Bugzilla 41913)
    • The handleAnalysis() method in the org.eclipse.xsd.impl.XSDComplexTypeDefinitionImpl.java class has been updated to handle an empty complex extension of a simple complex type. For example, it can now handle the following schema:
      <?xml version="1.0" encoding="UTF-8"?>
      <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
          <xsd:complexType name="ServiceCategory">
              <xsd:simpleContent>
                  <xsd:extension base="xsd:boolean"/>
              </xsd:simpleContent>
          </xsd:complexType>
          <xsd:element name="DialARide">
              <xsd:complexType>
                  <xsd:complexContent>
                      <xsd:extension base="ServiceCategory"/>
                  </xsd:complexContent>
              </xsd:complexType>
          </xsd:element>
      </xsd:schema>
      
    • The version numbers for the plugins in the feature.xml files have been updated to 1.1.1. Additionally, in the feature.xml file for the org.eclipse.xsd feature, the following updates have been made in the requires element:
      • in the import element for the org.eclipse.core.resources plugin, the version has been changed to 2.1.1
      • in the import element for the org.apaches.xerces plugin, the version has been changed to 4.0.13
      • in the import element for the org.eclipse.emf.ecore plugin, the version has been changed to 1.1.1
    • The duplicate value feature has been fixed in the org.eclipse.xsd.ecore.XSD2EcoreBuilder.java class. For example, for a schema like this:
      <?xml version = "1.0" encoding = "UTF-8"?>
      <xsd:schema xmlns:xsd = "http://www.w3.org/2001/XMLSchema">
      
              <xsd:complexType name = "ServiceCategory">
                      <xsd:simpleContent>
                              <xsd:extension base = "xsd:boolean"/>
                      </xsd:simpleContent>
              </xsd:complexType>
      
              <xsd:element name = "DialARide">
                      <xsd:complexType>
                              <xsd:complexContent>
                                      <xsd:extension base = "ServiceCategory"/>
                              </xsd:complexContent>
                      </xsd:complexType>
              </xsd:element>
      
      </xsd:schema>
      
      The EClass for DialARide previously had a second boolean feature named value1 that is now eliminated.

  5. Build 20031020_1612WL: Bug Fixes and Improvements
  6. There are bug fixes and improvements included with this build, some of which are described below. Where the description is for a bug reported through Bugzilla, the Bugzilla number is included after the description.

    • The import of a null namespace no longer generates a warning. (Bugzilla 43171)
  7. Build 20031120_1149WL: Bug Fixes and Improvements
  8. There are bug fixes and improvements included with this build, some of which are described below. Where the description is for a bug reported through Bugzilla, the Bugzilla number is included after the description.

    • Support configurable handling of schemaLocation resolution via org.eclipse.xsd.util.XSDSchemaLocationResolver (Bugzilla 46188)

What's new in XSD 1.1.0?

  1. Build 20030501_0612VL: Bug Fixes and Improvements
    1. New Plugins

      The xsd2ecore plugins (org.eclipse.emf.mapping.xsd2ecore and org.eclipse.emf.mapping.xsd2ecore.editor) have been added. They illustrate how to use the mapping framework, and the editor can be used to view the mapping produced during XSD to Ecore conversion. Documentation will be forthcoming soon.

    2. Bugzilla Fixes There are numerous bug fixes and improvements included with this build, some of which are described below. Where the description applies to a fix for a bug reported through Bugzilla, the Bugzilla number is included after the description.
      • XSD_ENCODING is now supported as an option for specifying the encoding for XSD resources.
      • The visibility of the isTypeDerivedFrom method in the XSDSchemaQueryTools class has been changed from protected to public. (Bugzilla 36062)
      • The XSD to Ecore conversion utilities have been moved to org.eclipse.xsd.ecore in the org.eclipse.xsd plugin for more flexible reuse.
  2. Build 20030513_0618VL: Bug Fixes and Improvements
  3. There are bug fixes and improvements included with this build, some of which are described below.

    • In order to have value objects that implement equals() correctly, values of simple types based on int[] and byte[] in Xerces need to be wrapped. Therefore, the types:
      • org.eclipse.xsd.types.XSDAnySimpleType.IntSequence and
      • org.eclipse.xsd.types.XSDAnySimpleType.ByteSequence
      will be used in place of int[] and byte[], respectively. (Later versions of Xerces have their own wrapper type which we will use when we switch to a newer version.)
    • We have refreshed the cached version of XMLSchema.xsd to the latest version on the web in order to pick up the errata changes to that version.
  4. Build 20030519_0521VL: Bug Fixes and Improvements
  5. There are bug fixes and improvements included with this build, some of which are described below. Where the description applies to a fix for a bug reported through Bugzilla, the Bugzilla number is included after the description. You can link directly to the Bugzilla bug using this number.

    • The XSD editor now detects the encoding of your XSD file and sets the encoding of the editor to match. (Bugzilla 37630).
    • The getBadTypeDerivation() method in XSDComplexTypeDefinitionImpl.java now handles a null base type.
    • XSD now populates the XSDFacet.annotation. (Bugzilla 37673).
    • XSDParser has been upgraded to support a LexicalHandler for creating Comment nodes.
    • XSDMainTest has been upgraded to support -validate for validating a schema from the command line.
  6. Build 20030527_0913VL: Bug Fixes and Improvements
  7. Minor bug fixes and improvements.

  8. Build 20030602_1759VL: Bug Fixes and Improvements
  9. This build is a refresh of XSD being delivered with the corresponding build of EMF.

  10. Build 20030605_1020SL: Bug Fixes and Improvements
  11. This build is a refresh of XSD being delivered with the corresponding build of EMF.

  12. Build 20030611_1435VL: Bug Fixes and Improvements
  13. There are bug fixes and improvements included with this build, some of which are described below. Where the description applies to a fix for a bug reported through Bugzilla, the Bugzilla number is included after the description. You can link directly to the Bugzilla bug using this number.

    • The following static methods in the org.eclipse.xsd.impl.XSDSchemaImpl.java class have been made synchronized:
      • createMetaSchema(Node node)
      • getGlobalResourceSet()
      • getMagicSchemaForSchema(String namespace)
      • getSchemaForSchema(String namespace)
      • getSchemaInstance(String namespace)
    • Complex type serialization now avoids the potential for introducing a redundant QName prefix.
    • The xsd2ecore mapping has been changed to map an XSD ID-type attribute as an ID EAttribute.
    • The xsd2ecore mapping has been updated to handle abstract elements and substitution groups.
    • XSD has been updated to recognize schema constraints referenced via include. (Bugzilla 38779)
    • The xsd2ecore editor has been updated to use translated strings for the name and description. (Bugzilla 38174)
  14. Build 20030616_1530VL: Bug Fixes and Improvements
  15. There are bug fixes and improvements included with this build, some of which are described below. Where the description applies to a fix for a bug reported through Bugzilla, the Bugzilla number is included after the description. You can link directly to the Bugzilla bug using this number.

    • The getEClassifier(XSDTypeDefinition xsdTypeDefinition, boolean supportNull) method in the org.eclipse.xsd.ecore.XSDEcoreBuilder.java class has been updated to ensure that an XSD abstract complex type becomes an abstract EClass.
    • The doSave(OutputStream os, Map options) method in the org.eclipse.xsd.util.XSDResourceImpl.java class has been updated so that if the schema element is null, the updateElement() method is called on the schema.
    • <package prefix=...> elements have been addded to the plugin.xml files for all the EMF and XSD plugins. (Bugzilla 38225)
    • The getBadTypeDerivation(XSDTypeDefinition xsdTypeDefinition, boolean extension, boolean restriction) method in the org.eclipse.xsd.impl.XSDSimpleTypeDefintionImpl.java class has been updated because a simple type needs to be considered to be derived from complex anyType.
    • The javadoc in the org.eclipse.xsd.XSDComplexTypeDefinition.java file has been updated for the XSDParticle getSyntheticParticle() method.
  16. Build 20030620_1105VL: Bug Fixes and Improvements
  17. There are bug fixes and improvements included with this build, some of which are described below.

    • National Language Support is now available for standalone clients.

What's new in XSD 1.0.2?

  1. Bug Fixes...
  2. Validation Support

    A schema can be validated to determine whether it is a fully valid instance according to the 1.0 specification; since this had been working for several months, it isn't really all that new.

What's new in XSD 1.0.1?

  1. Bug Fixes...
  2. Documentation Plugin

    There is now a documentation plugin, org.eclipse.xsd.doc, included in the download. All the XSD documentation is now available from the desktop Help menu. We've put the documentation plugin into the Runtime zip file, so its download size has increased. We're thinking about moving it into the Source zip, or maybe into its own zip file, in the future. If you have an opinion, please feel free to post it to the XSD newsgroup.

Search CVS

Releases