Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Merging schemas

From: Boris Kolpackov <boris@-------------.--->
To: Rich Adili <Rich.Adili@----.--->
Date: 8/17/2007 10:29:00 PM
Hi Rich,

Rich Adili <Rich.Adili@x...> writes:

> <DataWrapperNode>&lt;DataNode&gt;yadyada&lt;/DataNode&gt;</DataWrapperNo
> de>
>
> I would like to run this thing through a code generator and what I need
> as output is code representing the union of the two. Does this problem
> have an elegant solution?

Most data binding tools (I assume that's what you mean by a code
generator) would allow you to extract the inner XML and parse/validate
it using the code generated for DataNode. If a data binding tool you
are using support customization, then you might be able to customize
the type generated for DataWrapperNode so that this parsing/validation
happens transparently to the user.


-Boris


-- 
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding

From nandakol@h... Mon Aug 20 08:10:01 2007
Received: from maggie.w


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