WSWS

WSWS0001E: The path "{0}" is not an absolute path.
WSWS0002E: The parent directory for directory "{0}" does not exist.
WSWS0003E: Protocol must be either "http" or "https", not "{0}".
WSWS0004E: Port must be a positive number, not "{0}".
WSWS0005E: An exception occurred while attempting to extract module "{0}" from the application EAR file into the file system. The exception is "{1}".
WSWS0006E: An exception occured while attempting to construct a WSDLParser on WSDL file "{0}" in module "{1}". The exceptions is "{2}".
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.
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}.
WSWS0009E: Caught an exception while saving input WSDL file {0} for module {1} to filename {2}. The exceptions is {3}.
WSWS0010E: Caught an exception while creating a working directory. The exception is {0}.
WSWS0011E: Caught an exception while trying to get an InputStream for file {0} in module {1}. The exception is {2}.
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.
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.
WSWS0015E: Caught an exception while trying to get an InputStream for file {0}. The exception is {1}.
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.
WSWS0018E: The module {0} does not contain a Web services binding file, {1}. Run the endptEnabler command on the EAR file before installing to add this file.
WSWS0019E: The resource bundle {0} for locale {1} could not be opened. Exception {2}
WSWS0020E: Internal Error: {0}
WSWS0021E: In the Web services Deployment Descriptor for module "{0}", there is no wsdl-file element for webservice-deployment descriptor number {1}.
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.
WSWS0023E: The Web services bindings file, {0}, for module {1} does not contain any properly formatted routerModules elements
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}".
WSWS0025E: Caught an Exception while copying a file. The source file is {0}. The target file is {1}. The exception is {2}.
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.
WSWS0027E: In the Web services Deployment Descriptor for module "{0}", there is no webservice-description-name element for webservice-deployment descriptor number {1}.
WSWS0028W: completeTask : Cannot close InputStream "{0}"
WSWS0029E: getServerName: MapModulesToServers : taskData did not contain a row for moduleURIString "{0}"
WSWS0030E: MapModulesToServersAccessor.getNodeNamesFromServerString: the string "{0}" does not have the correct syntax.
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}.
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}.
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.
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.
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.
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.
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).
WSWS0038E: Error from Web services deploy tool: {0}
WSWS0039W: Warning from Web services deploy tool: {0}
WSWS0040I: Message from Web services deploy tool: {0}
WSWS0041I: Web services deploy task completed successfully.
WSWS0042E: The Web services bindings file for module {0} contains router module stanza whose transport type is neither jms nor http, but, incorrectly, {1}
WSWS0043E: The EJB module {0} does not have an associated router module
WSWS0044E: Cannot locate the deploy target for module: {0}
WSWS0045E: The router WAR module for EJB module {0} is {1}, but its web.xml is missing a url pattern for port component {2}.
WSWS0046E: The JMS router MDB module {0} does not contain a WebSphere IBM binding file.
WSWS0047E: Cannot find any WSDL files to publish.
WSWS0048I: Web services endpointenabler task completed successfully.
WSWS0049E: The EJB URL suffix {0} is not correctly formatted. It must have the form <property_name>=<value>[&<propety_name>=<value>], where the valid property_names are {1}. For example {2}
WSWS0050E: The Web services client bind file, ibm-webservicesclient-bnd.xmi, contains port type {0} which is not a valid port type for this client.
WSWS0051W: Custom Property parameter configured for {0} module {1} was ignored.
WSWS0052E: Preferred port mapping could not be created for module {0} client Web service {1}
WSWS0053E: The port {0} is not valid for port type {1} for Web service {2}, module {3}{4}
WSWS0054E: The JMS URL prefix {0} is not correctly formatted.
WSWS0055E: The value for Web service scope, {0}, for a port in module {1} is invalid.
WSWS0056E: The value for Web service client request timeout, {0}, for a port in module {1} is invalid.
WSWS0057E: The value for Web service client overridden endpoint URL, {0}, for a port in module {1} is invalid.
WSWS0058E: The deployed WSDL, {0}, could not be found for the Web service client in module {1}.
WSWS0059E: The Web service client overridden binding namespace, {0}, for module {1} cannot be specified if the overridden endpoint URL is not defined.
WSWS0060W: 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.
WSWS0061W: The JMS URL prefix {0} follows the IBM proprietary JMS URL syntax, which has been deprecated.


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.webservices.deploy.resources.deployMessages.dita
File name: com.ibm.ws.webservices.deploy.resources.deployMessages.html