IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Incorrect WSDL generation in EntireX Workbench?

  • 1.  Incorrect WSDL generation in EntireX Workbench?

    Posted Mon April 15, 2002 11:23 AM

    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.


    #webMethods
    #EntireX
    #Mainframe-Integration


  • 2.  RE: Incorrect WSDL generation in EntireX Workbench?

    Posted Fri April 26, 2002 11:45 AM

    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.


    #Mainframe-Integration
    #webMethods
    #EntireX


Related Content