|
|
 next
|
  Subject: I find a BUG in stylus studio 2008 xml Enterprise
Author: (Deleted User)
Date: 09 Dec 2008 02:53 AM
|
Hi Xu,
when you use a single XML instance as model for your source, it is representing an entire class of XML files, so Stylus Studio must generalize it. For instance, it could have a <item> node with a <magazine> children, then another <item> with <newspaper>; in this case, Stylus would show a schema tree with <item> having two children, <magazine> and <newspaper>. In your case, there must be a <pro> item with a <pro> children, so it means that potentially they can recurse.
If you want to disambiguate the schema, you will need to use an XSD schema as representation of the input data, in which the second <pro> is clearly defined as a different structure (i.e. it's not the same type of the parent).
Alberto
|
|
next
|
Subject: I find a BUG in stylus studio 2008 xml Enterprise
Author: (Deleted User)
Date: 09 Dec 2008 08:49 AM
|
Hi Xu,
if you want a precise schema tree in XSLT Mapper, you need to provide a schema; otherwise, if you provide just a single XML instance file, the schema will be "fuzzy" and treat all the elements having the same element name as being variants of the same single global type.
The kind of schema tree you are referring to is the one displayed in the text view of the XSLT editor, where you see the content of the stylesheet, and a right pane with the exact content and structure of the XML file currently used as data source. On the other hand, the mapper view uses the left and right schema trees as schema source, not data sources, so their behaviours are different.
Hope this clears the picture,
Alberto
|
|
|
|
|
groupseq.xml
top