Originally posted by: uvaiseodam

Hi,

I want to generate the below xml after the map.

Issue: Schema location namespaces are not getting generated after the transformation.

Scenario: Created a type tree from a wsdl and after transformation map is not generating child namespaces and prefixes. Default parent namespace is getting assigned for all fields by default. I am using WTXv  8.4.1.4. But when try to create a sample request for the same wsdl in soapui all namespaces with their proper prefixes and namespaces are getting generated. I cannot share original wsdl due to some constraints. Anu pointers on this would be really appreciated.TIA.

<Parent xmlns="http://org.db.com/Api/1.0/"> 
         <request xmlns:a="http://schemas.contract.org/2004/07/DB.Api">
            <a:Tickets xmlns:b="http://schemas.contract.org/2004/07/DB.Models">
               <b:Ticket>
                  <b:CorrelationId>0D2D0553-3F77-43C4-9DB5-BDF860A03D46</b:CorrelationId>
               </b:Ticket>
            </a:Tickets>
        </request>
</Parent>

Originally posted by: PaulBrett

There is a known issue with WTX 8.4.1 generating the .MTX file correctly.

I was able to use ITX 9.0.0 to generate the .MTX file, and then use that to create this map in WTX 8.4.1.  The map produces this output:

<Parent>
<request>
<a:Tickets xmlns:b="http://schemas.contract.org/2004/07/DB.Models" xmlns:a="http://schemas.contract.org/2004/07/DB.Api">
<b:Ticket>
<b:CorrelationId>0D2D0553-3F77-43C4-9DB5-BDF860A03D46</b:CorrelationId>
</b:Ticket>
</a:Tickets>
</request>
</Parent>
 

Thank you.

Paul

Follow me on Twitter

Attachment(s)

Namespace.zip   8 KB 1 version

Originally posted by: uvaiseodam

Thank you Paul. It worked.

I created type tree in ITX and used the same type tree in 8.4.1 and it worked. But i didn't see any .mtx file in the project. Do you know where to locate this file?

Thanks,

Uvaise Ahmed

Originally posted by: PaulBrett

Uvaise,

I assumed that you were using the XSD natively.  With an import, a .MTX file is not created.

It is the equivalent of an on-the-fly importer.

Thank you.

Paul

Follow me on Twitter