Originally posted by: SystemAdmin

We are trying to create a Type tree, by importing xml schema in import wizard of Type Designer.

But application crashes because of errors (screen shot attached).

And the schema files has been validated in XMLSpy. So what could the reason ?
I have also attached the schema files and log file.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

It works OK if you use Clasic validation.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

code
<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSPY v2004 rel. 3 U (http://www.xmlspy.com)-->
<baseCBECoreType xmlns="http://ossj.org/xml/Common-CBECore/v1-3" xmlns:co-v1-3="http://ossj.org/xml/Common/v1-3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ossj.org/xml/Common-CBECore/v1-3
C:\TEMP\OSSJ-Common-CBECore-v1-3.xsd"/>
[/code]

I can't generate any meaningfiul sample xml from XMLSpy. Is your schema correct?

#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

Something seems to go down an infinite number of levels in the xml.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

It is a valid file schema file, though we posted only two schema files(base schema files).

We could generate sample xml from, XMLSpy, it depends on the root element selected, and also selected fill data in elements & attributes,

<co-v1-3:getEventDescriptorException xsi:schemaLocation="http://ossj.org/xml/Common-CBECore/v1-3 OSSJ-Common-CBECore-v1-3.xsd" xmlns:co-v1-3="http://ossj.org/xml/Common/v1-3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<co-v1-3:ossIllegalArgumentException>
<co-v1-3:message>String</co-v1-3:message>
</co-v1-3:ossIllegalArgumentException>
</co-v1-3:getEventDescriptorException>


#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Thanks, we tried it with using classic validation, it worked.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: janhess

unfortunately the resulting type tree is missing most of it's elements.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

The ttmaker log contains lots of references to Invalid type name.
I think these relate to things like co-v1-3:UpdateProcedureValue which don't seem to be defined in the schema. I can't find any reference to the types which contain co-v1-3:
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

I am not sure about log file, do not understand it.

But now (after selecting classic validation in import) nearly all elements are available in Type tree (type + element).

I checked in XMLSpy, in Components box, if you count (element + complexType), no of elements are nearly the same. The difference of 1-2 items, atleast one of element missing is xs:anyType, visible in XMYSpy not in WTX Type tree.

Also checked in Websphere Integration Developer(WID), importing into SCA Library, the Data Types count is nearly the same, difference of 1-2. Atleast one 'baseCBECoreType' is not visible in WID, as it a element(type CBECoreType).

The 'UpdateProdureValue' is available in OSSJ-Common-v1-3.xsd(co-v1-3:), as a complexType.

So most of the elements are visible.

Thanks & regards,
Manoj.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange