WSWS

WSWS1000E: Error: {0}
WSWS1001E: The client process service cannot be accessed.
WSWS1002E: An error occurred while processing the Web services deployment descriptor for module: {0} with error: {1}
WSWS1003E: The WSDL file that is referenced by the client deployment descriptor service reference {0} contains no services.
WSWS1004E: An error occurred while binding client references in java:{0} namespace: {1}
WSWS1005E: The DTD reference in the Web services deployment descriptor is not valid: {0}
WSWS1007E: More than one service is in the WSDL file, but service reference {0} in the client deployment descriptor does not specify which service QName to use.
WSWS1008W: Unable to dump the configuration as part of debug: {0}
WSWS1009W: Warning: [{0}:{1}:{2}] {3}
WSWS1010E: Error: [{0}:{1}:{2}] {3}
WSWS1011E: Error: [{0}:{1}:{2}] {3}
WSWS1012E: Error: Web services is missing the Web container.
WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
WSWS1014W: Java class {0} that is specified in provider {1} cannot be loaded. The provider is skipped. The exception is {2}.
WSWS1015W: Servlet for servlet-link {0} not found. The port-component {1} is skipped.
WSWS1016E: Multiple ''port-component-name'' elements with the value {0} were found.
WSWS1017E: The JSR 109 JAX-RPC mapping file {0}, as specified in the client deployment descriptor for service reference {1} cannot be read.
WSWS1018W: For handlers {0} the handler {1} was not added due to a role statement {2} that is not valid.
WSWS1019W: For handlers {0} the handler {1} is not added because of a flow statement {2} that is not valid.
WSWS1020E: Unable to parse file {0}
WSWS1021W: Warning: No services to deploy.
WSWS1022W: Client reference {0} not of expected type {1} in java:comp namespace.
WSWS1023W: The client reference was not found in java:comp namespace.
WSWS1025E: Error: Resource {0} was not found.
WSWS1026E: Error: Resource {0} was not loaded: {1}
WSWS1027W: Warning: Web services MBean could not be registered: {0}
WSWS1028E: Error: Unable to initialize EJBCollaborator: {0}
WSWS1029E: Error: {0}: Metadata service lookup failed: {1}
WSWS1030E: An error occurred while binding service references: {0}
WSWS1031E: {0}: An error occurred while binding service references in the java:{1} namespace.
WSWS1032E: {0}: An error occurred while binding service reference {1} in the java:{2} namespace.
WSWS1033W: Java class {0} that is specified for handler {1} cannot be loaded. The handler is skipped. The exception is {2}.
WSWS1034W: No port component binding with the name {0} was found in bindings file {1}.
WSWS1035E: An error occurred in {0}: context information: {1}
WSWS1037E: The JSR 109 JAX-RPC mapping file {0}, as specified in <webservice-description> {1} in deployment descriptor {2} for module {3} was not found in application {4}. This Web service description is ignored.
WSWS1038W: No setter method on {0} with a method name {1} was found for reference {2}. The service name cannot be changed to {3}.
WSWS1039E: The Web services binding file {0} was not found in module {1} in application {2}. This file is required for this type of module.
WSWS1040W: The Web services binding file {0} was not found in module {1} in application {2}. Certain functionality, such as Web services security is not available.
WSWS1041W: No Web service description binding is found in the Web services binding file {0} with the name {1}.
WSWS1042E: An error occurred in loading the configuration for {0}. The exception is {1}.
WSWS1043E: An error occurred in the configuration. More than one security binding is defined, but the program cannot determine which one to use without the WSDL service port.
WSWS1044E: An error occurred in the configuration. More than one security deployment descriptor is defined, but the program cannot determine which one to use without the WSDL service port.
WSWS1045E: An error occurred in loading {0} configuration for {1}. The service cannot be started.
WSWS1046E: The ibm-webservices-bnd.xmi file for enterprise bean module {0} says that the associated router module is {1}. However, that router module does not exist in the application.
WSWS1047W: The ibm-webservicesclient-bnd.xmi defaultMappings information for serviceRefLink {0} does not correspond to the information in the WSDL file. One or more of the following values are incorrectly specified in the ibm-webservicesclient-bnd.xmi file: portTypeLocalName {1}, portTypeNamespace {2}, portLocalName {3}, or portNamespace {4}.
WSWS1048E: J2EE 1.3 {0} contains unexpected component-scoped service references with no component specified.
WSWS1049E: J2EE 1.3 {0} is missing component-scoped service references.
WSWS1050W: J2EE 1.3 {0} component-scoped service references do not match the enterprise beans.
WSWS1051W: The Web service-enabled enterprise bean does not have any defined Web service router modules.
WSWS1052E: The service endpoint is not defined. Application ''{0}'', Module ''{1}'', enterprise bean ''{2}''.
WSWS1053E: The service endpoint of the ejb-jar.xml ({0}) and webservices.xml ({1}) files do not match. Application ''{2}'', Module ''{3}'', enterprise bean ''{4}''.
WSWS1054E: Internal Error: An EJB object is expected at dispatcher invoke.
WSWS1055E: Internal Error: An EJB object is expected at dispatcher cleanup.
WSWS1056E: Internal Error: The method ''{0}'' on class ''{1}''was not found.
WSWS1057E: Internal Error: The Web services global configuration was not loaded.
WSWS1058E: Application {0}, module {1}, file {2}, port-component-name {3}: service-impl-bean ejb-link {4} does not correspond to any enterprise bean name in the ejb-jar.xml file.
WSWS1059E: No WSDL services exist with qname {0}.
WSWS1060E: Received request {0} for unregistered system service endpoint {1}.
WSWS1061E: No system endpoint router is defined for request {0}.
WSWS1062I: The SOAP Container service has been initialized.
WSWS1063E: No Web services system service is available.
WSWS1064E: A transport header key of null or length of zero is specified. This header key is not valid and will be ignored.
WSWS1065E: A transport header value of null or length of zero is specified for header key {0}. This header key is not valid and will be ignored.
WSWS1066W: {0} in {1} does not contain a componentScopedRefs element, which is required for configuring security.
WSWS1067E: The loading of the metadata for JAX-RPC module {0} has failed. The exception is: {1}
WSWS1068E: Internal error. A response from a web service endpoint in an Enterprise Java Beans module could not be processed because an endpoint manager could not be located.


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.resources.webservicesMessages.dita
File name: com.ibm.ws.webservices.resources.webservicesMessages.html