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.
Prohibited attributes in restriction

Prohibited attributes in restriction

2004-02-12       - By Dirk Reiss
Reply:     1     2     3     4  

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Greif wrote:
| I think prohibited substitutions refers to substitution groups.  An
element
| E1 can be declared to be the "head" of a substitution group.  If another
| element E2 is of a type derived from E1's type, it may declare that it
is a
| member of E1's substitution group, allowing E2 to be used wherever E1
could
| be used.  If E1 is a member of a substitution group headed by E0, then E2
| can also substitute for E0.
|
| But E1 is allowed to prohibit substitution of elements for it which are
| derived by restriction or elements derived by extension (while
allowing the
| other).  Also, individual places where E1 is used may make similar
| prohibitions, I think.
|
| I don't think this has much to do with your prohibited attribute use.
|
| Jeff

Hello again,

thank you very much for your clarification, i think i went into the
wrong direction with that.

Anyway, as this method has nothing to do with my problem:
How could i find out about the prohibition of an attribute by restriction?

Thanks again,
Dirk
|
|
| ----- Original Message -----
| From: "Dirk Reiss" <d.reiss@(protected)>
| To: <xerces-j-user@(protected)>
| Sent: Thursday, February 12, 2004 4:29 PM
| Subject: Prohibited attributes in restriction
|
|
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Hello everyone,
|>
|>using org.apache.xerces.xs - API, i would like to retrieve the
|>information, if an attribute is prohibited in an inherited complex type
|>definition. Could anyone give me a short idea of how to do so or a small
|>code example?
|>
|>Furthermore, i assume that
|>XSComplexTypeDefinition.getProhibitedSubstitutions() has something to do
|>with that task, but i do not really understand the usage of this function.
|
|
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
| For additional commands, e-mail: xerces-j-user-help@(protected)
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALCxBEJAsP020pFcRAoAEAJ40rixd+jOweasf8MbNk31+Z0l5DgCcCSgR
kQoAUGWdLSjW1quKqKNGSHc=
=Y7KF
-----END PGP SIGNATURE-----

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