Hi!
I don't know if this is right place to ask, but I tryed many places and still don't have an answer :-(
I have application that uses complex XSD schemas. Also some elements & types can be customized by end user.
We using something like:
--------- s1.xsd ---------
sometypes
-----------------------------
-------- s2.xsd ---------
redefine of s1.xsd
<!-- end user ads here some customization -->
----------------------------
-------- s3.xsd --------
include s2.xsd
<!-- actual elements here -->
--------------------------
So the application uses customized version of elements. But we can't break cycle in following schema:
--------------------
<xsd:complexTyp e name="customerT ype">
<xsd:sequence >
<xsd:element name="rootCusto mer" ref="customer"/>
<!-- ... -->
</xsd:sequence>
</xsd:complexType >
<xsd:element name="customer" type="customerT ype"/>
--------------------
So the question: how to implement end user customization for this case?
I don't know if this is right place to ask, but I tryed many places and still don't have an answer :-(
I have application that uses complex XSD schemas. Also some elements & types can be customized by end user.
We using something like:
--------- s1.xsd ---------
sometypes
-----------------------------
-------- s2.xsd ---------
redefine of s1.xsd
<!-- end user ads here some customization -->
----------------------------
-------- s3.xsd --------
include s2.xsd
<!-- actual elements here -->
--------------------------
So the application uses customized version of elements. But we can't break cycle in following schema:
--------------------
<xsd:complexTyp e name="customerT ype">
<xsd:sequence >
<xsd:element name="rootCusto mer" ref="customer"/>
<!-- ... -->
</xsd:sequence>
</xsd:complexType >
<xsd:element name="customer" type="customerT ype"/>
--------------------
So the question: how to implement end user customization for this case?