March 2008 - oXygen-user - www.oxygenxml.com

Can't increase stack size.
by Gavin Kistner 17 Mar '08

17 Mar '08

Oxygen is overflowing the stack trying to validate one of my XML files against its schema. However, if I modify this file: C:\Program Files\Oxygen XML Editor 9\oxygen.vmoptions from this: -Xmx700m to this: -Xmx700m -Xss1024k Oxygen fails to start. I select it from the Start Menu and get this message: Error The JVM could not be started. The main method may have thrown an exception. If I delete the Xss option again it works. I've tried values of 512k, 512 and 1024k. This is on XP SP2 with Oxygen build 2007121417 Should the options be on multiple lines? Any help on how I can increase the stack size? FWIW, the failure seems to be on this attribute: <xs:attribute name="values"> <xs:simpleType><xs:restriction base="xs:string"> <xs:pattern value="(-?(\d+|\d*\.\d+)(,-?(\d+|\d*\.\d+))?;)*-?(\d+|\d*\.\d+)(,-?(\d+|\d*\.\d+))?"></xs:pattern> </xs:restriction></xs:simpleType> </xs:attribute> with this value: values="0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109" Is there any way to turn off backtracking for the regexp, which presumably would help here?

3 3

Confusing Message When Schema Cannot Be Found
by Eliot Kimber 11 Mar '08

11 Mar '08

In testing my catalog's ability to resolve this document's schema: <?xml version="1.0" encoding="UTF-8"?> <test xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:foo:/schemas/test.xsd" ></test> When the catalog was not correctly configured Oxygen 9.1 reported "There is no schema or DTD associated with the document". But what it really needed to say is "cannot find schema at schema location "urn:foo:/schemas/test.xsd". I thought it was complaining about the form of my schema attributes. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 1

xml database
by Boojum 11 Mar '08

11 Mar '08

Anybody have any experience using / integrating Oxygen with a native XML database like Exist, Sedna or Xindice? How about with an XML content management system?

2 1

How Does Oxygen Validate This Dublin Core Schema?
by Eliot Kimber 10 Mar '08

10 Mar '08

In testing our own schema-based validation features in our RSuite product we discovered that as far as we can tell Xerxes 2.9.x fails to validate the valid Dublin Core schema given below. This is a documented problem with Xerces in that it doesn't handle the particular pattern of restriction and substitution groups used in this schema. However, Oxygen happily (and correctly) validates documents using this schema (that is, our test case fails when we parse it with our Xerces-based code but Oxygen reports it as valid). My understanding was that Oxygen used Xerces for its schema processing, so my question is: what does Oxygen do special that allows it to process this case, or is our understanding of Xerces flawed? The failure we get is than an instance of e.g., dc:title is reported by Xerces as not allowing character data content when of course it does. The original discussion of this issue from the Dublin Core people is here: http://dublincore.org/schemas/xmls/qdc/2008/02/11/notes/ Very near the bottom is this: This derivation of a complexType with simpleContent by restriction of a base complexType with complexContent is valid under section 3.4.6 of XML Schema Part 1: Structures, specifically item 5.1.2 of the section "Schema Component Constraint: Derivation Valid (Restriction, Complex)", because the base complexContent is mixed and emptiable. This was confirmed by Henry Thompson, see e.g. http://www.w3.org/2001/05/xmlschema-rec-comments#pfiSimpleContent http://lists.w3.org/Archives/Public/xmlschema-dev/2002Oct/0005.html http://lists.w3.org/Archives/Public/xmlschema-dev/2002Oct/0008.html Conclusion: Xerces appears to be behaving incorrectly in rejecting this derivation. Thanks, Eliot <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://purl.org/dc/elements/1.1/" targetNamespace="http://purl.org/dc/elements/1.1/" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:documentation xml:lang="en"> DCMES 1.1 XML Schema XML Schema for http://purl.org/dc/elements/1.1/ namespace Created 2003-04-02 Created by Tim Cole (t-cole3(a)uiuc.edu) Tom Habing (thabing(a)uiuc.edu) Jane Hunter (jane(a)dstc.edu.au) Pete Johnston (p.johnston(a)ukoln.ac.uk) Carl Lagoze (lagoze(a)cs.cornell.edu) This schema declares XML elements for the 15 DC elements from the http://purl.org/dc/elements/1.1/ namespace. It defines a complexType SimpleLiteral which permits mixed content and makes the xml:lang attribute available. It disallows child elements by use of minOcccurs/maxOccurs. However, this complexType does permit the derivation of other complexTypes which would permit child elements. All elements are declared as substitutable for the abstract element any, which means that the default type for all elements is dc:SimpleLiteral. </xs:documentation> </xs:annotation> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/03/xml.xsd"> </xs:import> <xs:complexType name="SimpleLiteral"> <xs:annotation> <xs:documentation xml:lang="en"> This is the default type for all of the DC elements. It permits text content only with optional xml:lang attribute. Text is allowed because mixed="true", but sub-elements are disallowed because minOccurs="0" and maxOccurs="0" are on the xs:any tag. This complexType allows for restriction or extension permitting child elements. </xs:documentation> </xs:annotation> <xs:complexContent mixed="true"> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/> </xs:sequence> <xs:attribute ref="xml:lang" use="optional"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="any" type="SimpleLiteral" abstract="true"/> <xs:element name="title" substitutionGroup="any"/> <xs:element name="creator" substitutionGroup="any"/> <xs:element name="subject" substitutionGroup="any"/> <xs:element name="description" substitutionGroup="any"/> <xs:element name="publisher" substitutionGroup="any"/> <xs:element name="contributor" substitutionGroup="any"/> <xs:element name="date" substitutionGroup="any"/> <xs:element name="type" substitutionGroup="any"/> <xs:element name="format" substitutionGroup="any"/> <xs:element name="identifier" substitutionGroup="any"/> <xs:element name="source" substitutionGroup="any"/> <xs:element name="language" substitutionGroup="any"/> <xs:element name="relation" substitutionGroup="any"/> <xs:element name="coverage" substitutionGroup="any"/> <xs:element name="rights" substitutionGroup="any"/> <xs:group name="elementsGroup"> <xs:annotation> <xs:documentation xml:lang="en"> This group is included as a convenience for schema authors who need to refer to all the elements in the http://purl.org/dc/elements/1.1/ namespace. </xs:documentation> </xs:annotation> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="any"/> </xs:choice> </xs:sequence> </xs:group> <xs:complexType name="elementContainer"> <xs:annotation> <xs:documentation xml:lang="en"> This complexType is included as a convenience for schema authors who need to define a root or container element for all of the DC elements. </xs:documentation> </xs:annotation> <xs:choice> <xs:group ref="elementsGroup"/> </xs:choice> </xs:complexType> </xs:schema> -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 3

browser
by Boojum 03 Mar '08

03 Mar '08

When I selected XML Document --> Open in Browser, nothing is displayed in the browser (my default browser is Firefox).

2 1