Interface editor Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
3.0 Known problems and workarounds
   3.1 Adding documentation to a one-way operation could produce an invalid WSDL file
   3.2 After changing the name of a Web service export, regenerate the bindings

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphereR Integration Developer interface editor.

2.0 Limitations

None

3.0 Known problems and workarounds

3.1 Adding documentation to a one-way operation could produce an invalid WSDL file

If you add documentation to a one-way operation, and then add an input to the same operation, an invalid WSDL file could be produced.

Here is the workaround: add an input to the operation, then add the documentation to the operation.

(Note: This is not an issue for request-response type operations.)

3.2 After changing the name of a Web service export, regenerate the bindings

If the name of a Web service export gets changed to something other than the default, the address (for example: <soap:address location="xxx: />) specified in the generated binding WSDL file will not get changed accordingly. This results in inconsistencies between where the actual endpoint is located and the address specified in the binding WSDL file.

Here is the workaround: Regenerate the binding file by right-clicking Export and selecting Replace Bindings. This generates a new binding file with the correct soap:address endpoint reflecting the renamed export. (This action will leave the originally generated binding file behind. It is safe to delete this old binding file.