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.
examining XML schema attributes

examining XML schema attributes

2003-07-24       - By Martin Lambert
Reply:     1     2     3     4     5     6     7     8     9  

Hi,

I am trying to examine schema attribute definintions using Xerces.  I am able
to retrieve information about attributes that includes an attribute name, its
type name and whether it is required.
However I want to retrieve more detailed information about the attribute's type
. For example, given the type definition below I would like to retrieve the
values that make up the enumeration i.e.
1,2,3,4,5. I can't seem to work out the correct approach to retrieving this
information. I would also like to know how this would work for a type with
restrictions like 'negative integer'.

I have also included my code to highlight how I have been trying to approach
this problem.

<simpleType name="testType">
        <restriction base="integer">
           <enumeration value="1"/>
           <enumeration value="2"/>
           <enumeration value="3"/>
           <enumeration value="4"/>
           <enumeration value="5"/>
        </restriction>
</simpleType>

<complexType name="classType">
   <sequence>
      <element name="template" type="templateType" maxOccurs="unbounded"/>
   </sequence>
   <attribute name="matches" type="testType" use="required"/>
</complexType>

Where element is an instance of 'XSElementDeclaration':

XSTypeDefinition elementTypeDef = element.getTypeDefinition();
XSObjectList attributeUses  = ((XSComplexTypeDefinition)elementTypeDef)
.getAttributeUses();

for(int attrUseIdx=0; attrUseIdx < attributeUses.getLength(); attrUseIdx++)
{
           XSAttributeUse attributeUse = (XSAttributeUse)attributeUses.item
(attrUseIdx);
           XSAttributeDeclaration attribute = attributeUse.getAttrDeclaration(
);
           XSSimpleTypeDefinition attributeType = attribute.getTypeDefinition(
);

           System.out.println(attribute.getName() + ", required? " +
attributeUse.getRequired() +
           ", bounded? " + attributeType.getBounded() + ", finite? " +
attributeType.getFinite() +
           ", numeric? " + attributeType.getNumeric() + ", type: " +
attributeType.getName() +
           ", constraint value: " + attribute.getConstraintValue() + ",
enumeration" attributeType);
}

Hope there is a straightforward answer to this.

Cheers,

Martin.


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