Previous | Next |
This example shows how a separate SCHEMA can also be provided to further normalize the data prior to binding. In this example the customer data is more structured. The <NAME> now consists of <FIRST>, <MIDDLE> and <LAST> parts which are specified in random order. Also the <DATE> is now stored as separate components <DAY>, <MONTH> and <YEAR>.
, |
|
The problem with this extra structure is that the schema generator now considers the <NAME> and <DATE> nodes as ROWSETS when they are never really going to be repeated. Having them become ROWSETS makes it much more effort to bind to the sub-fields. So to avoid this extra work, you can hand-tune the schema that is generated by removing the unwanted ROWSETS and then provide this in a SCHEMA <PARAM> on the <APPLET> tag as follows:
, |
|
The XML DSO Source Code is in Java.
© 1997 Microsoft Corporation. All rights reserved. Legal Notices.