WSWS

WSWS0001E: The path "{0}" is not an absolute path.
Explanation The name of the published WSDL file must be a fully qualified and absolute path name.
Action Provide an absolute path name for the published WSDL file.
WSWS0002E: The parent directory for directory "{0}" does not exist.
Explanation The directory that the published WSDL file is to be placed must already exist.
Action Specify an existing directory for the published WSDL file.
WSWS0003E: Protocol must be either "http" or "https", not "{0}".
Explanation The only valid choices for the protocol are "http" and "https".
Action Specify either "http" or "https".
WSWS0004E: Port must be a positive number, not "{0}".
Explanation Port must be a positive number.
Action 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.
Action 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.
Action 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.
Action Correct either or both of the files so that they match.
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.
Action 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.
Action 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.
Action 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.
Action 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 for the Web service enabled jar file has a routerModuleName 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 in the application's application.xml file.
Action Make sure that the endptEnabler command 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.
Action 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.
Action 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.
Action Add the expected WSDL file.
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.
Explanation A Web service enabled module must contain a Web services binding file.
Action Add the missing binding file using either the Assembly Toolkit or the endptEnabler command.
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.
Action If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
WSWS0020E: Internal Error: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
WSWS0021E: In the Web services Deployment Descriptor for module "{0}", there is no wsdl-file element for webservice-deployment descriptor number {1}.
Explanation The Web services deployment descriptor is not properly formed. One possible reason is that its Web service description elements do not have an associated WSDL file.
Action Correct the deployment descriptor.
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 Web services deployment descriptor is not properly formed. One if its webservice-description elements has an improperly formed port component element.
Action Correct the deployment descriptor.
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.
Action Correct 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.
Action Correct 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.
Action 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.
Action 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 Web services Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a webservice-description-name element.
Action Correct the deployment descriptor.
WSWS0028W: completeTask : Cannot close InputStream "{0}"
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
WSWS0029E: getServerName: MapModulesToServers : taskData did not contain a row for moduleURIString "{0}"
Explanation This is a programming error. All the modules should have server names.
Action This exception is unexpected. The cause is not immediately known.
WSWS0030E: MapModulesToServersAccessor.getNodeNamesFromServerString: the string "{0}" does not have the correct syntax.
Explanation This is a programming error. Assume that the MapModulesToServers task should have already validated that the user input has the correct syntax.
Action This exception is unexpected. The cause is not immediately known.
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.
Action Correct the WEB-INF/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-INF/web.xml file contains an error.
Action Correct the WEB-INF/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.
Action Correct the WEB-INF/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.
Action Remove the inconsistency 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.
Action Make sure that the endptEnabler command is run on the application and that the application contains the required router module.
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 module's web.xml is not correct.
Action 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 specifications allowed the wsdl-file element of the Web services 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).
Action Move all WSDL files to the wsdl directory.
WSWS0038E: Error from Web services deploy tool: {0}
Explanation Web services deploy tool reported an error, the deployment may have failed.
Action Examine the error message from WSDeploy tool to determine the source of the problem.
WSWS0039W: Warning from Web services deploy tool: {0}
Explanation Web services deploy tool reports a warning, the deployment may or may not fail.
Action Examine the warning message from WSDeploy to determine whether any corrective action is necessary.
WSWS0040I: Message from Web services deploy tool: {0}
Explanation None.
Action No action required.
WSWS0041I: Web services deploy task completed successfully.
Explanation The Web services deploy task has completed successfully.
Action No action required.
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. The supported transports for router modules include jms and http.
Action Correct the Web services bindings file and re-try.
WSWS0043E: The EJB module {0} does not have an associated router module
Explanation For all Web services enabled EJB module, at least one router module has to be created within the same application
Action Run endptEnabler to add appropriate router modules.
WSWS0044E: Cannot locate the deploy target for module: {0}
Explanation All applications have to be deployed into either a server or a cluster environment.
Action Correct the deployment.xml for 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.
Action 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 exception is unexpected. The cause is not immediately known.
Action If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
WSWS0047E: Cannot find any WSDL files to publish.
Explanation All Web services enabled applications should have at least one WSDL file.
Action If the application is Web services enabled, check to see whether WSDL files are packaged with the application.
WSWS0048I: Web services endpointenabler task completed successfully.
Explanation The Web services endpointenabler task has completed successfully.
Action There is no action required.
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}
Explanation Incorrect user input for EJB URL suffix.
Action Provide correct input.
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.
Explanation There is an inconsistency in the Web services client configurartion.
Action Ensure that the WSDL file configured for this client contains the port type.
WSWS0051W: Custom Property parameter configured for {0} module {1} was ignored.
Explanation Only element zero of the custom property parameters object is used.
Action Ensure that the properties configured are combined into the first parameter element.
WSWS0052E: Preferred port mapping could not be created for module {0} client Web service {1}
Explanation A problem occurred while creating a mapping of port types and the ports that could be configured for them. This information is generated from the client deployment descriptor and the WSDL file.
Action Ensure that Web services client in this module is probably configured and the WSDL file identified in the client deployment descriptor is in the module.
WSWS0053E: The port {0} is not valid for port type {1} for Web service {2}, module {3}{4}
Explanation A Web service client preferred port must implement its port type. The client WSDL file specifies ports, bindings and port types.
Action Specify a preferred port that implements the port type.
WSWS0054E: The JMS URL prefix {0} is not correctly formatted.
Explanation The JMS URL prefix was not formatted correctly. The JMS URL prefix must start with jms:jndi: followed by the destination JNDI name, and it must include the jndiConnectionFactoryName property. The destination and connection factory JNDI names must not contain java:comp.
Action Provide correct input.
WSWS0055E: The value for Web service scope, {0}, for a port in module {1} is invalid.
Explanation Incorrect user input provided for Web service scope.
Action Provide correct input. Correct values are Application, Request, and Session.
WSWS0056E: The value for Web service client request timeout, {0}, for a port in module {1} is invalid.
Explanation Incorrect user input provided for Web service client resquest timeout. The timeout is number of milliseconds to wait for a request to complete.
Action Provide correct input. The value must be a positive integer, 0, or -1.
WSWS0057E: The value for Web service client overridden endpoint URL, {0}, for a port in module {1} is invalid.
Explanation The user input provided for Web service client overridden endpoint URL is not a valid URL.
Action Provide correct input. The value must be a valid URL that represents an HTTP port, JMS port, or a local ejb.
WSWS0058E: The deployed WSDL, {0}, could not be found for the Web service client in module {1}.
Explanation The user input provided for Web service client's deployed WSDL is not valid.
Action Provide correct input. The deployed WSDL value must be a uri relative to the module and represent a WSDL file that is in the client's module.
WSWS0059E: The Web service client overridden binding namespace, {0}, for module {1} cannot be specified if the overridden endpoint URL is not defined.
Explanation The overridden binding namespace cannot be specified unless the overridden endpoint URL is specified or previously defined.
Action Provide a value for Web service client overridden endpoint URL or do not specify a value for the overridden binding namespace.
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.
Explanation One of the WSDL files in a module is inconsistent with the Web services deployment descriptor.
Action Remove the inconsistency, either by removing the port from the WSDL file or adding a corresponding port-component to the deployment descriptor.
WSWS0061W: The JMS URL prefix {0} follows the IBM proprietary JMS URL syntax, which has been deprecated.
Explanation The user entered a JMS URL prefix string which starts with "jms:/queue" or "jms:/topic" which indicates that it follows the IBM proprietary JMS URL syntax. The IBM proprietary JMS URL syntax has been deprecated in favor of the industry standard JMS URL syntax.
Action Change your JMS URL prefix string so that it follows the industry standard JMS URL syntax. Consult the product documentation for more information.
Reference topic    

Terms and conditions for product documentation | Feedback

Last updated: Apr 17, 2017 8:10:18 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.deploy.resources.deployMessages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)