# Idl extractor for WSDL.

**URL:** <https://techcommunity.softwareag.com/t/idl-extractor-for-wsdl/97269>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [May 30, 2011, 4:30pm UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-wsdl/97269 "2011-05-30T16:30:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Pelaez](https://avatars.discourse-cdn.com/v4/letter/d/edb3f5/32.png) [@David\_Pelaez](https://techcommunity.softwareag.com/u/David_Pelaez)\
**Post date:** [May 30, 2011, 4:30pm UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-wsdl/97269/1 "2011-05-30T16:30:07Z")

</div>

Hi,  
I have generated xmm file from a WSDL using the Eclipse plugin (Workbench).  
XMLRPCServer 7.3.4 (trying 7.3.3 gives the same problem)  
Workbench 7.3.3  
I have registered xmm file with de WS URL as a target server.  
I make the CALLNAT from Natural and it’s works. The request arrives to XMLRPCServer, the XMLRPCServer comunicates with the WS. Data goes and return to XMLRPCSERVER. Translation from XMLRPCServer to Natural generates the problem.

exx.sdk.java.rpc.log (everything OK on that file)

Thank you very much for your attention.  
Any suggestion will be wellcome.  
Sorry for my bad English.  
[SWXSgsp.xmm.txt](https://techcommunity.softwareag.com/uploads/short-url/f5KwQXBs6nbvF1oktr9pCEEnTdz.txt) (119 KB)  
[traceWithTheError.txt](https://techcommunity.softwareag.com/uploads/short-url/e6BVxzOii5DvSrPchy9LzU9AhT2.txt) (1.09 KB)  
[exx.sdk.java.rpc.txt](https://techcommunity.softwareag.com/uploads/short-url/bfv3ibGD2pO7rsEaMg6xDEvzkb.txt) (141 KB)

---

<div class="post-metadata">

**Author:** ![Matthew](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@Matthew](https://techcommunity.softwareag.com/u/Matthew)\
**Post date:** [May 31, 2011, 5:36pm UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-wsdl/97269/2 "2011-05-31T17:36:22Z")

</div>

Hi David,

You error, 2000 0077, indicates that the XML Runtime cannot interpret the incoming document. In this case it is the Web Service response it cannot interpret. There are a number of reasons why this might happen, maybe the most common of them all being that the response document used a different namespace than expected.  
Later versions of EntireX have changed some so that this type of an error is quite rare.  
I do not have a comparable environment but I believe you need only alter the namespace URI in the XML Mapping to match the web services namespace. Just deleting the value in the Mapping editor may also work.

I would normally suggest you open a support request but I see you are using a very old version of EntireX which is no longer supported. You should really consider upgrading to EntireX 8.2.1 which was just recently released.

Regards

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [June 14, 2011, 7:04pm UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-wsdl/97269/3 "2011-06-14T19:04:50Z")

</div>

The XMM specifies a namespace “[http://sicalwin.sw.aytos](http://sicalwin.sw.aytos)” for all elements.

However, the response from the web service contains this namespace for the elements consultaOpeGastosPreviasResponse and return only. But not for cabeceraGastos, opg\_acf etc.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:00pm UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-wsdl/97269/4 "2021-04-02T15:00:19Z")

</div>