Page 2 of 2

Posted: Mon Oct 22, 2007 2:15 am
by himerius
But since the xsd says its a closed start tag, the output xml should also produce a closed start tag, and not this </resolution> end tag?

Posted: Mon Oct 22, 2007 2:37 am
by janhess
I don't understand what wou mean by a 'closed start tag'. </Resolution> is the closing tag for <Resolution>. It will only produce a /> close if the tag is empty and required.

Posted: Mon Oct 22, 2007 3:09 am
by himerius
The tags are empty, the value is in the v attribute, as dictaded by the xsd?
not a xsd wiz though..

Posted: Tue Oct 23, 2007 6:09 am
by janhess
I think it produce the closed start tag if you import the xsd using the classic importer. Xerces seems to do slightly different things.

In classic import you get a terminator such as <OWSP></DecimalFormatString<OWSP>>
and an Empty Value <OWSP><DecimalFormatString<OWSP>/>

Posted: Thu Nov 08, 2007 2:26 pm
by himerius
Lol, just discovered, its not dtx that makes the long version of the tag, its the browsers that ends it.

inet explorer and dtx preview:
- <Interval>
<Position v="1" />
<Quantity v="3.5" />
</Interval>

Actual file:
<Interval>
<Position v="1"></Position>
<Quantity v="3.5"></Quantity>
</Interval>

Posted: Thu Nov 08, 2007 8:51 pm
by ray.wurlod
Clearly Microsoft knows better than you do exactly what you need!
:roll:

Posted: Fri Nov 09, 2007 3:32 am
by janhess
I've never seen that behaviour in IE before.