Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Problem with ref-attributes and schema validation

Problem with ref-attributes and schema validation

2007-06-17       - By Asgeir Frimannsson
Reply:     1     2     3  

Hi Michael,

Thanks for this clarification.

cheers,
asgeir

On 6/18/07, Michael Glavassevich <mrglavas@(protected)> wrote:
> Hi Asgeir,
>
> What you're observing is normal. The prefixes used in schema documents
> don't get carried over into the schema component model [1] or defaulted
> attributes [2] (just the local name and namespace URI). Note that
> sax.Writer is just a sample for users to learn how to use SAX. It doesn't
> do everything a real namespace-aware serializer should do like namespace
> fixup: selecting suitable prefixes for elements/attributes and adding the
> necessary namespace declarations to the document to make it well-formed.
>
> Thanks.
>
> [1] http://www.w3.org/TR/xmlschema-1/#Attribute_Declaration_details
> [2] http://www.w3.org/TR/xmlschema-1/#d0e8328
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@(protected)
> E-mail: mrglavas@(protected)
>
> "Asgeir Frimannsson" <asgeirf@(protected)> wrote on 06/14/2007 07:39:47 AM:
>
> > Hi all,
> >
> > I have come across something that _might_ be a bug in xerces. Let me
> > explain by example:
> >
> > Given the following schema:
> >
> > <xsd:schema
> >    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> >    xmlns:xml="http://www.w3.org/XML/1998/namespace"
> >    elementFormDefault="qualified"
> >    targetNamespace="http://www.example.com">
> >
> >    <!-- Import for xml:space -->
> >    <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
> >       schemaLocation="http://www.w3.org/2001/xml.xsd"/>
> >
> >    <xsd:element name="animal">
> >       <xsd:complexType mixed="true">
> >          <xsd:attribute ref="xml:space" default="preserve"/>
> >          <xsd:attribute name="name" type="xsd:string" use="required"/>
> >       </xsd:complexType>
> >    </xsd:element>
> >
> > </xsd:schema>
> >
> > Notice the xml:space attribute has a default value 'preserve'. Now,
> > given the following instance:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <animal xmlns="http://www.example.com" xmlns:x="http://www.example.com"
> >       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >       xsi:schemaLocation="http://www.example.com SpaceBug.xsd"
> >    name="dog">
> >   hi, i'm a dog
> > </animal>
> >
> > Note that no value is set for xml:space, so I expect xerces to insert
> > this for me when doing schema validation. To make the possible bug
> > simple to reproduce, I'll use one of the xerces samples for validating
> > and writing this document. Using the following options:
> > Namespace processing: on
> > Namespace prefixes: on
> > Validation: on
> > Schema validation support: on
> > Schema full checking: on
> >
> > java sax.Writer -n -np -s -f -v instance.xml
> >
> > ...which produces the following output:
> >
> > <animal name="dog" space="preserve" xmlns="http://www.example.com"
> > xmlns:x="http://www.example.com"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://www.example.com SpaceBug.xsd">
> >   hi, i'm a dog
> > </animal>
> >
> > Notice how the xml:space attribute is now unqualified. This is
> > reproducable for any namespace, not just the special xml namespace.
> >
> > I initially bumped into this problem when using the XOM library
> > (reported [1]), and it seems that the namespace uri is correctly set
> > when inserting the default value, but the prefix is lost.
> >
> > cheers,
> > asgeir
> >
> > [1]
> http://lists.ibiblio.org/pipermail/xom-interest/2007-June/003484.html
> >
> > --
> > Asgeir Frimannsson
> > PhD Candidate
> > School of Software Engineering and Data Communications
> > Queensland University of Technology
> > 126 Margaret Street, Level 3
> > Brisbane QLD 4001, Australia
> >
> > Phone: (+61) 7 3138 9332 Mob: (+61) 405 412 696
> > Email: asgeirf@(protected)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
> > For additional commands, e-mail: j-dev-help@(protected)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
> For additional commands, e-mail: j-dev-help@(protected)
>
>


--
Asgeir Frimannsson
PhD Candidate
School of Software Engineering and Data Communications
Queensland University of Technology
126 Margaret Street, Level 3
Brisbane QLD 4001, Australia

Phone: (+61) 7 3138 9332 Mob: (+61) 405 412 696
Email: asgeirf@(protected)

---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)