Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


XML data binding and schema styles

From: "Andrew Welch" <andrew.j.welch@-----.--->
To: xml-dev@-----.---.---, ----@--------.------.---
Date: 10/9/2007 10:01:00 AM
I asked the questions below on the user@x... mailing
list but haven't had a reply yet - a more general question for this
list is: do schema styles make a siginificant difference when it comes
to data-binding?  As in, "if you are using binding tool x, you should
use style y"?  Or is there a style that suits all data binding, and a
style that definitely doesn't?

The XMLBeans specific question was:

==

I'm using XMLBeans for data binding (for the first time) which is
generating classes for all top-level elements with the name
nnnnDocument, such as priceDocument for the global element price,
dateDocument for date etc

The schema style I've used is the salami slice style, where each
element is known globally.  This means the schema can potentially be
used for schema aware XSLT / XQuery (which require that the elements
are known globally).

Is there any way to supply XMLBeans with the element to use as the
root element, such that only the generated class for that element ends
with "Document", and not the others ?

Does XMLBeans and the salami slice style of schema not go well together ?

==

thanks

-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/


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