Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


overriding the schema at runtime..

From: dave <ceek63@-----.--->
To: user@--------.------.---, -------@-----.---.---
Date: 4/7/2008 4:45:00 PM
Is it possible to override the w3c XSD at runtime?
For e.g., I would like to make 'processContents' =
Skip or Lax instead of Strict in the following schema
during run time:
<xs:complexType name="ExtType">
	<xs:sequence>
	   <xs:any namespace="##any" processContents="strict"
minOccurs="0" maxOccurs="50"/>
	</xs:sequence>
</xs:complexType>


In other words, I am trying to avoid changing the
schema and thus create a new schema version just for
this small change. I primarily introduced 'ExtType'
above for schema extension so that any further changes
(like application specific) to the schema using this
part should not affect the validation. I tried adding
an extra element (both with and without namespace)
using the above type and the schema validation failed.
Finally found out that making processContents = 'skip'
is the solution to introduce any new application
specific elements with no namespace.



-D


      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent