Originally posted by: repanzer1
Before a particular version of WTX, not sure if is 8.1 or earlier, you could only import a DTD one way. After that particular version, you had the option of importing using Xerces. I do not know the differences in what happens behind the scenes when doing either import method, but I do know the type trees created are different.
When the DTD is imported via the classic method, I can click on any field in the XML, and it will bring up the properties as if it were any other type of file. I can see the Initiator and Terminator in the Type Syntax section, and can make changes to the tag information.
When the DTD is imported via the Xerces method, when you bring up the properties, it has different information in the properties area, and has a section which says "Intent>XML >Validate As>XML Element >Name, Mixed, Abstract, ProcessContents, etc". Basically, it has all these options that I cannot change. When I open the Type Syntax area, none of the fields are populated. I cannot see the tag information, let alone update it.
In the event I have to change a tag name and the type tree was built as a Xerces import, as of now, I would have to update the tag name in the DTD and import it again. If I had to change a tag name in a type tree imported in the classical method, I would just have to go to the Type Syntax and update it.
What I'm really hoping someone could explain is how I can do simple task, such as updating a tag name when the type tree is imported using Xerces. But, any information regarding why the type designer acts this way and what advantages using the new Xerces method offers, because at this point, it seems like a step backwards. It seems silly that I'd have to re-import the entire DTD and build a whole new type tree, just to accomplish a task as simple as changing a tag name.
Thank you!!
There are 10 types of people in this world. Those who understand binary and those who don't.
#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender#DataExchange