WebSphere Web ServicesWSWS0001E: The path "{0}" is not an absolute path.
Explanation
The name of the published WSDL file must be an fully qualified, absolute, path name.
User Response:
Provide an absolute path.
WSWS0002E: The parent directory for directory "{0}" does not exist.
Explanation
The directory into which the published WSDL file is to be placed must already exist.
User Response:
Name an existing directory.
WSWS0003E: Protocol must be either "http" or "https", not "{0}".
Explanation
The only valid choices for the protocol are "http" and "https".
User Response:
sSpecify either "http" or "https".
WSWS0004E: Port must be a positive number, not "{0}".
Explanation
Port must be a positive number.
User Response:
Provide a positive number.
WSWS0005E: An exception occurred while attempting to extract module "{0}" from the application EAR file into the file system. The exception is "{1}".
Explanation
The exception details should provide additional information.
User Response:
The exception details should give guidance on what to do.
WSWS0006E: An exception occured while attempting to construct a WSDLParser on WSDL file "{0}" in module "{1}". The exceptions is "{2}".
Explanation
The exception details should provide additional information.
User Response:
The exception details should give guidance on what to do.
WSWS0007E: The Web Services Deployment Descriptor "webservices.xml" for module {0} has a webservice-description element whose wsdl-file element is "{1}". The webservice-description element contains a port-component element with the elements port-qname-namespace = {2} and port-qname-localname = {3}. The wsdl file must contain a targetNameSpace whose value matches the binding file's port-qname-namespace, and it must contain a port whose name attribute matches the port-qname-localname.
Explanation
The values in the wsdl file and the Web Services Deployment Descriptor must match up.
User Response:
Correct one of the files.
WSWS0008E: Cannot set the soap address into the published WSDL file. Failed when calling WSLDParser.setSoapAddress() with wsdlNameSpace={0}, wsdlPortName={1}, and soapAddressURI={2}. The input WSDL file is {3} for module {4}.
Explanation
There may be a syntax error in the input WSDL file.
User Response:
Check the input WSDL file for any errors.
WSWS0009E: Caught an exception while saving input WSDL file {0} for module {1} to filename {2}. The exceptions is {3}.
Explanation
Could not create output WSDL file.
User Response:
The exception details should give some guidance.
WSWS0010E: Caught an exception while creating a working directory. The exception is {0}.
Explanation
Could not create a working directory.
User Response:
The exception details should give some guidance.
WSWS0011E: Caught an exception while trying to get an InputStream for file {0} in module {1}. The exception is {2}.
Explanation
Could not get the InputStream.
User Response:
The exception details should give some guidance.
WSWS0012E: Failed while looking in the application ear file''s application.xml for a web module whose name is {0}. Perhaps the EndpointEnabler has not been run on the application.
Explanation
The ibm-webservice-bnd.dtd file of Web Service enabled jar file has routeModuleName attribute whose value does not match any web module described in the application's application.xml file. Or, a Web Service enabled war file does not appear i the application's application.xml file.
User Response:
Check the ibm-webservice-bnd.dtd and application.xml files. Make sure the endpointEnabler has been run on the ear file.
WSWS0013E: The module {0}''s Web Services Deployment Descriptor, webservices.xml, has a wsdl-file element for the file {1}. However, the module's bindingfile, {2}, doesn't have a ws-desc-binding element for that WSDL file.
Explanation
There is a mismatch between the information in the Web Services Deployment Descriptor and the information in the Web Services Binding file.
User Response:
Make the two files consistent.
WSWS0015E: Caught an exception while trying to get an InputStream for file {0}. The exception is {1}.
Explanation
The exception details should provide additional information.
User Response:
The exception details should give some guidance.
WSWS0016E: The webservices.xml file for module {0} refers to WSDL file "{1}", but the module does not contain a WSDL file by that name.
Explanation
If a webservices.xml file has a reference to a WSDL file then that WSDL file must exist in the module.
User Response:
Add the expected WSDL file.
WSWS0018E: The module {0} does not contain a Web Services binding file, {1}.
Explanation
A Web Service enabled module must contain a Web Services binding file.
User Response:
Add the missing binding file.
WSWS0019E: The resource bundle {0} for locale {1} could not be opened. Exception {2}
Explanation
The resource bundle for your locale was not found. This will prevent logging of information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS0020E: Internal Error: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS0021E: In the Web Services Deployment Descriptor for module "{0}", there is no wsdl-file element for webservice-deployment descriptor number {1}.
Explanation
The WebServices Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a wsdl-file element.
User Response:
Fix the DeploymentDescriptor.
WSWS0022E: In the Web Services Deployment Descriptor for module "{0}", the portcomponent element number {1} of webservice-description element number {2} is not properly formed.
Explanation
The WebServices Deployment Descriptor is not properly formed, one if its webservice-description elements has an improperly formed portcomponent element.
User Response:
Fix the DeploymentDescriptor.
WSWS0023E: The Web Services bindings file, {0}, for module {1} does not contain any properly formatted routerModules elements
Explanation
The Web Services binding file does not contain a properly formatted "routerModules" element.
User Response:
Fix the bindings file.
WSWS0024E: A Web Services enabled EJB-JAR module must be deployed to the same server as its router module. However the EJB-JAR module "{0}" is deployed to "{1}" while its router module. "{2}" is deployed to "{3}".
Explanation
Each EBJ-JAR file must have a related router WAR module.
User Response:
Fix the application.
WSWS0025E: Caught an Exception while copying a file. The source file is {0}. The target file is {1}. The exception is {2}.
Explanation
An IOException occurred while copying a file.
User Response:
The exception details should give some guidance.
WSWS0026E: The file system name "{0}" is needed for a directory in the published WSDL file tree. However, the name already exists in the file system and is not a directory.
Explanation
There is a name conflict between directory and file system name.
User Response:
Remove the file.
WSWS0027E: In the Web Services Deployment Descriptor for module "{0}", there is no webservice-description-name element for webservice-deployment descriptor number {1}.
Explanation
The WebServices Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a webservice-description-name element.
User Response:
Fix the DeploymentDescriptor.
WSWS0028W: completeTask : Cannot close InputStream "{0}"
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS0029E: getServerName: MapModulesToServers :taskData did not contain a row for moduleURIString "{0}"
Explanation
This is a programming error. All the modules shouldhave server names.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS0030E: MapModulesToServersAccessor.getNodeNamesFromServerString: the string "{0}" does not have the correct syntax.
Explanation
This is a programming error. Assume that theMapModulesToServers task should have already validated thatthe user input has the correct syntax.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS0031E: If a servlet is linked to a webservice.xml file'''s port-component, then the module'''s web.xml file must contain no more than one servlet-mapping for that servlet. However, in module {0}, web.xml contains more than one servlet-mapping element for servlet {1}.
Explanation
The web.xml file contains an error.
User Response:
Repair the web.xml file.
WSWS0032E: If a servlet is linked to from a webservice.xml file'''s port-component, and the module'''s web.xml file contains a url-pattern for that servlet, then the url-pattern must be an exact match pattern, that is it must not contain an asterisk("*"). However, in module {0}, web.xml contains a url-pattern of {1} for servlet {2}.
Explanation
The web.xml file contains an error.
User Response:
Repair the web.xml file.
WSWS0033E: In the webservices.xml file for a Web Services enabled WAR module, a port-component''s service-impl-bean must be servlet-link, not an EJB-link. However in module {0}, webservice.xml has a port-component named {1} whose service-impl-bean is not a servlet-link.
Explanation
The webservices.xml file contains an error.
User Response:
Repair the webservices.xml file.
WSWS0034E: In module {0}, the WSDL file {1} contains a port named {2}, but there is no corresponding port component in the Web services deployment descriptor.
Explanation
One of the WSDL files in a module is inconsistent with the Web Services deployment descriptor.
User Response:
remove the inconsistency, either by removing the port from the WSDL file or adding a corresponding port-component to the Deployment Descriptor.
WSWS0035E: The ibm-webservices-bnd.xml for EJB module {0} says that the associated router WAR module is {1}. However that WAR module does not exist in the application.
Explanation
The router war module is missing from the application.
User Response:
Fix the application.
WSWS0036E: {0} is the router module for Web Services enabled module {1}. The router modules web.xml file must contain a servlet-mapping stanza with a url-pattern and a servlet-name of {2}, but it does not.
Explanation
The router WAR's web.xml is not correct.
User Response:
Make sure the servlet-mapping element is there and that it contains a url-pattern.
WSWS0037W: The module {0} contains WSDL file {1}. It is recommended that WSDL files reside in or below WEB-INF/wsdl (for WAR modules) and META-INF/wsdl (for JAR modules).
Explanation
Older versions of Web Services specification allowed the wsdl-file element of the WebServices Deployment Descriptor to point anywhere in the module. The current version recommends that all WSDL files reside in or below WEB-INF/wsdl (for WAR modules) and META-INF/wsdl (for JAR modules).. In the future, WSDL files that do not reside in or below the appropriate wsdl directory will not be published to URI, or to file.
User Response:
Move all WSDL files to the wsdl directory.
WSWS0038E: Error from WebServices deploy tool: {0}
Explanation
WebServices deploy tool reported an error, the deployment may have failed.
User Response:
Examine the error message from WSDeploy tool to determine the source of the problem.
WSWS0039W: Warning from WebServices deploy tool: {0}
Explanation
WebServices deploy tool reports a warning, the deployment may or may not fail.
User Response:
Examine the warning message from WSDeploy to determine whether any corrective action is necessary.
WSWS0040I: Message from WebServices deploy tool: {0}
Explanation
None.
User Response:
None.
WSWS0041I: WebServices deploy task completed successfully.
Explanation
The WebServices deploy task has completed successfully.
User Response:
None.
WSWS0042E: The Web Services bindings file for module {0} contains router module stanza whose transport type is neither jms nor http, but, incorrectly, {1}
Explanation
The Web Services bindings file has incorrect information
User Response:
Correct the Web Services bindings file
WSWS0043E: The EJB module {0} does not have an associated router module
Explanation
For all WebServices enabled EJB module, at least one router module has to be created within the same application
User Response:
Run endpointEnabler to add appropriate router modules
WSWS0044E: Can not locate the deploy target for module: {0}
Explanation
All applications have to deployed into either a server or a cluster.
User Response:
Correct the deployment.xml for this the application or reinstall the application.
WSWS0045E: The router war module for EJB module {0} is {1}, but its web.xml is missing a url pattern for port component {2}.
Explanation
The web.xml for the router war module should have one url pattern for each port component defined within webservices.xml.
User Response:
Correct the web.xml for this router module.
WSWS0046E: The JMS router MDB module {0} does not contain a WebSphere IBM binding file.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS0047E: Can not find any publishable WSDL files.
Explanation
All WebServices enabled applications should have at least one wsdl file.
User Response:
If the application is WebServices enabled, check to see whether wsdl files are packaged with the application.