SDO bugs? why cannot convert DOMSource to SDO?

[ext2 <xu...@tongtech.com>]

Hi:
	I have defined a type and a global element in my schema;
A file store a xml which format is same as the global element defined in
schema;
If I using SDO's XMLHelper loading the xml file as SDO, the result will be
successfully;

But if I loading the xml file to a w3c Element, and wrapping the Element
using a DOMSource; Then using XMLHelper loading the DOMSource as SDO, the
result will be failed.  The  SDO's type cannot not recognized by SDO. Only a
SDO:AnyType object is returned;
	I am sure the loaded W3C Element is right, because if I save the
loaded XML Element back to a String, then convert the String to  SDO, the
result will be right;

	Why? Is SDO's bug?

Following is my schema and source code:
<xs:element name="st1E" type="ns:ST1"/>
<xs:complexType name="ST1">
	<xs:sequence>
		<xs:element name="a1" type="xs:string"/>
	</xs:sequence>
</xs:complexType>

The xml is :
<st1E xmlns="http://test/sometype">
  <a1>test</a1>
</st1E>

java SDO XmlHelper cannot parse DOMSource to SDO correctly.

[ext2 <xu...@tongtech.com>]

Hi:
	In my application , I need convert the XML stored as
org.w3c.dom.element to SDO Object; 
	The XMLHelper support a method which can load the Source to SDO
Document.
But if I using this method to load DOMSource as SDO,  it cannot work
correctly. The result SDO's type is AnyType, and is not correct schema
registered in SDO type context;
	But if I convert the DOM to string first, then load the string as
SDO, the result is correct. Although it work, but this way will waste
performance.
	Why ?
	Does any know how to using TUSCANY SDO to convert DOMSource as sdo ?

Following is a sample xml
<xs:element name="st1E" type="ns:ST1"/>
<xs:complexType name="ST1">
	<xs:sequence>
		<xs:element name="a1" type="xs:string"/>
	</xs:sequence>
</xs:complexType>

The xml is :
<st1E xmlns="http://test/sometype">
  <a1>test</a1>
</st1E>