How to treat name spaces when manually importing XML calls

Expert Answer Center > Experts On Demand > View Answer

EMAIL THIS

Experts on Demand

EXPERTS ON DEMAND HOME

POSE A QUESTION

VIEW ANSWERS

BROWSE BY TOPIC

RSS FEEDS

A team has defined a service in multiple files. Each file except the one containing the types has a WSDL extension. The schema file, of course, has a XSD extension. The service is defined in one file and everything else is cascaded imports into it. I don't have a lot of time to learn the XML calls to take nodes and copy them into one file. But I tried manually copy and pasting the sections into one combined file and ran into problems. I used a program called XML Spy by Altova Corp., but it does not complain. The program that uses the combined file does complain. The problem is in the namespaces. How am I supposed to treat namespaces when I manually perform the import with a location task? Is there a tool that interprets the imports and creates a combined WSDL file?

QUESTION POSED ON: 13 FEB 2006
QUESTION ANSWERED BY: Ed Tittel

In general, referencing multiple namespaces requires using the correct form of reference to identify them when they're uses in the body of an XML document. This subject matter is both tricky and requires special handling, but also well-documenting and relatively easy to learn and master. You'll want to read some or all of the following references to help you solve your problem:

XML.com: Using W3C XML Schema -- deals with importing and referencing multiple namespaces in the context of XML Schema documents
HP Devsource "Using XML Schemas Effectively in WSDL Design" -- especially the section on "Using XML namespaces effectively"
CPAN: XML Namespace -- Simple Support for XML Namespaces -- especially the section on "Importing XML::Namespace Objects"

This should be enough to get you started down the road you'll need to walk to make things work in your situation. My guess is that namespaces are either not being imported and identified properly in the document preamble/header, or they're not being referenced using correct nomenclature in the document body.

HTH, and thanks for posting.

--Ed--

TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.


TechTarget Corporate Web Site \| Media Kits \| Site Map All Rights Reserved, Copyright 2009, TechTarget \| Read our Privacy Policy