# Incorrect WSDL generation in EntireX Workbench?

**URL:** <https://techcommunity.softwareag.com/t/incorrect-wsdl-generation-in-entirex-workbench/58871>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [April 15, 2002, 3:22pm UTC](https://techcommunity.softwareag.com/t/incorrect-wsdl-generation-in-entirex-workbench/58871 "2002-04-15T15:22:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michel\_de\_Blok](https://avatars.discourse-cdn.com/v4/letter/m/50afbb/32.png) [@Michel\_de\_Blok](https://techcommunity.softwareag.com/u/Michel_de_Blok)\
**Post date:** [April 15, 2002, 3:22pm UTC](https://techcommunity.softwareag.com/t/incorrect-wsdl-generation-in-entirex-workbench/58871/1 "2002-04-15T15:22:49Z")

</div>

Currently we are using EntireX 6.1.1.0 for a project for one of our customers. We use the SOAP 1.1 mapping to create an XML Adapter and generate a WSDL to invoke this ‘webservice’.  
  
The problem is, that when I open this WSDL in IBM’s Websphere Studio Application Developer the ‘link’ between the generated Port and the generated Port Type is missing. Experimenting with WSDL4J showed the same problem.  
  
It seems that there has to be a target namespace prefix (tns:) in /definitions/binding/@type and /definitions/service/port/@binding. After adding this prefix, WSDL4J ‘expands’ the WSDL document correctly and it also works in WSAD.  
  
Is the generated WSDL by EntireX not in confirmation with the W3C standard? Or does WSDL4J make assumptions regarding the target namespace that is incorrect? Personally, I assume the first since WSDL4J is being developed as a JSR and used in many Java programs based on WSDL.

---

<div class="post-metadata">

**Author:** ![Dietmar\_Gartner](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/dietmar_gartner/32/127_2.png) [@Dietmar\_Gartner](https://techcommunity.softwareag.com/u/Dietmar_Gartner)\
**Post date:** [April 26, 2002, 3:45pm UTC](https://techcommunity.softwareag.com/t/incorrect-wsdl-generation-in-entirex-workbench/58871/2 "2002-04-26T15:45:29Z")

</div>

Michel,  
  
this problem has been fixed in a subsequent update to EntireX 6.1.1. I’d suggest you apply the latest patch (number 8) to your EntireX installation.  
  
Regards, Dietmar.

---

<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, 2:39pm UTC](https://techcommunity.softwareag.com/t/incorrect-wsdl-generation-in-entirex-workbench/58871/3 "2021-04-02T14:39:31Z")

</div>