Web Services 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 Limitations
   1.1 Cannot install UDDI on DB2 in Windows if the server install path contains spaces
2.0 Known problems and workarounds
   2.1 WebSphere Web Service WSDL URL displays incorrectly
   2.2 Web Services wizard (Windows only) hangs when creating new Web service on WebSphere Application Server v6.0
   2.3 Command line Web service creation scripts might fail with certain -project argument

1.0 Limitations

1.1 Cannot install UDDI on DB2 in Windows if the server install path contains spaces

You might encounter problems when installing a UDDI Registry using DB2® on Windows® if the WebSphere® Application Server installation path contains spaces (for example, if the WebSphere Application Server is installed on  C:\Program Files\IBM\WebSphere\AppServer). This causes the creation of the UDDI registry on DB2 database to fail.

 You will not see an error and the scenario will create a DB2 database and deploy the UDDI Application to the server. However the database will not be prefilled with information necessary for the UDDI registry to work. This results in the UDDI node not being created and not being added to the server.

 To resolve this issue, install WebSphere Application Server in a path that does not contain spaces (for example: C:\IBM\WebSphere\AppServer).

 

 

2.0 Known problems and workarounds

2.1 WebSphere Web Service WSDL URL displays incorrectly

When a workspace contains more than one running WebSphere Web service, some of the URLs under the WebSphere Web Service category inside the Web Services Explorer's WSDL Browser or Discovery Dialog will show an incorrect port component name. The URL pattern that may be incorrect will be of the form:

 .../services/L<port component name>?WSDL

 for example,

 .../services/LEcho?WSDL

 To resolve this, use the workspace WSDL locator.

2.2 Web Services wizard (Windows only) hangs when creating new Web service on WebSphere Application Server v6.0

There is an issue with directory lengths for WebSphere Application Server v6.0 which can result in the workbench not responding during the creation of a Web service deployed to WebSphere Application Server v6.0 when using the Web services wizard . The problem occurs when WebSphere Application Server v6.0 catches an exception due to not being able to fully process the .wsdl file for the .war being generated. The WebSphere process enters an endless loop, however the Web Services wizard is not notified that this has occurred and is deadlocked. Because the wizard cancel button is disabled at this point in the process, there appears no way to cancel the publishing other than to terminate the workbench process.


 

The workaround is to be conscious when working with WebSphere Application Server v6.0 which has this known file/directory limitation on Windows and to keep profiles in as short as an install location as possible, for example, c:\profiles. By default the profiles may be installed into a fairly deep path and at some point files attempted to be written to the profiles temporary directory will fail with an IO exception that halts the publishing.

2.3 Command line Web service creation scripts might fail with certain -project argument

The command line Web service creation scripts (WSDL2WebService, WSDL2WebService13, WSDL2Client, WSDL2Client13) may fail when running from the root directory.  Create a working directory and ensure the "-project" argument is a pointing to a directory inside the working directory.