|
WebSphere Web Services messages |
|
WSWS0001E: 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:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS0020E: Internal Error: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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 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 Web services 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 Web services 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 exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 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 theMapModulesToServers task should have already validated thatthe user input has the correct syntax.
User Response:
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.
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 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).. 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 Web services deploy tool: {0}
Explanation:
Web services 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 Web services deploy tool: {0}
Explanation:
Web services 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 Web services deploy tool: {0}
Explanation:
None.
User Response:
None.
WSWS0041I: Web services deploy task completed successfully.
Explanation:
The Web services 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 Web services 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 exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS0047E: Can not find any WSDL files to publish.
Explanation:
All Web services enabled applications should have at least one wsdl file.
User Response:
If the application is Web services enabled, check to see whether wsdl files are packaged with the application.
WSWS1000E: Error: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS1001E: Error - Could not access the client process service.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS1002E: Error processing Web services deployment descriptor for module: {0} with error: {1}
Explanation:
Unable to construct a Web services deployment descriptor.
User Response:
Review error (exception stack trace) for root cause.
WSWS1003E: There are no services in the WSDL file referenced by Client DD service reference {0}.
Explanation:
There are no services defined in the WSDL file.
User Response:
Modify the WSDL file to include at least one service definition.
WSWS1004E: Error binding client references in java:{0} namespace: {1}
Explanation:
Unable to bind client references into the JNDI namespace.
User Response:
This exception is unexpected. The cause is not immediately known.
WSWS1005E: Invalid DTD reference in Web services deployment descriptor: {0}
Explanation:
Invalid DTD reference in Web services deployment descriptor.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS1007E: There is more than one service in the WSDL file but service reference {0} in the Client DD does not specify which service QName to use.
WSWS1008W: Unable to dump 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 missing WebContainer.
WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
WSWS1014W: Javaclass {0} specified in provider {1} could not be loaded. The provider will be skipped. The exception is {2}.
WSWS1015W: Servlet for servlet-link {0} not found. The port-component {1} will be skipped.
WSWS1016E: Found multiple port-component-name elements with the value {0}.
WSWS1017E: The JSR 109 JAX-RPC mapping DD file {0} as specified in the Client DD for service reference {1} could not be read.
WSWS1018W: For handlers {0} the handler {1} was not added due to an invalid role statement {2}
WSWS1019W: For handlers {0} the handler {1} was not added due to an invalid flow statement {2}
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: Client reference not found in java:comp namespace.
WSWS1024W: Invalid service reference {0} found in module {1} in file {2}.
WSWS1025E: Error: Resource {0} not found.
WSWS1026E: Error: Resource {0} not loaded: {1}
WSWS1027W: Warning: Web services MBean could not be registered: {0}
WSWS1028E: Error: Unable to initialize EJBCollaborator: {0}
WSWS1029E: Error: {0}: Meta Data service lookup failed: {1}
WSWS1030E: Error binding service references: {0}
WSWS1031E: Error: {0}: Error binding service references in java:{1} namespace.
WSWS1032E: Error: {0}: Error binding service reference {1} in java:{2} namespace.
WSWS1033W: Javaclass {0} specified for handler {1} could not be loaded. The handler will be skipped. The exception is {2}.
WSWS1034W: No port component binding with the name {0} was found in bindings file {1}.
WSWS1035E: Exception caught in {0}: context info: {1}
WSWS1037E: The JSR 109 JAX-RPC mapping DD file {0} as specified in
WSWS1038W: No setter on {0} with a method name {1} found for reference {2}. The service name could not be changed to {3}.
WSWS1039E: The IBM 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 IBM Web services binding file {0} was not found in module {1} in application {2}. Certain functionality such as WS-Security will not be available.
WSWS1041W: No Web service description binding was found in the IBM Web services binding file {0} with the name {1} .
WSWS1042E: Error in loading configuration for {0}. The exception is {1}.
WSWS1043E: Error in the configuration. There are more than one security bindings defined, but can not determined which one to use without the WSDL service Port.
WSWS1044E: Error in the configuration. There are more than one security deployment descriptors defined, but can not determined which one to use without the WSDL service Port.
WSWS1045E: Error in loading {0} configuration for {1}. The service can not be started.
WSWS1046E: The ibm-webservices-bnd.xml for EJB module {0} says that the associated router module is {1}. However that the 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 are incorrectly specified in the ibm-webservicesclient-bnd.xmi file: portTypeLocalName {1}, portTypeNamespace {2}, portLocalName {3}, and/or portNamespace {4}.
WSWS1048E: The port type {0} of a preferred port in the ibm-webservicesclient-bnd.xmi was not found.
WSWS1049E: The WSDL file {0} could not be opened.
WSWS1050E: No service references were found in the deployment descriptor.
WSWS2000I: {0}
WSWS2001I: Trace data will be displayed on stdout.
WSWS2002I: Please enter the name of an existing file.
WSWS2003I: Backing up EAR file to: {0}~
WSWS2004I: IBM WebSphere Application Server Release 5
WSWS2005I: Web services Enterprise Archive Endpoint Enabler Tool.
WSWS2006I: Please enter the name of your EAR file:
WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2003.
WSWS2008E: Missing value for '-transport' parameter.
WSWS2009E: Missing value for '-properties' parameter.
WSWS2010I: Read properties from file: {0}
WSWS2011E: ERROR: unrecognized command-line parameter found: {0}
WSWS2012I: The endpoint enabler is using the following properties:
WSWS2013E: Unrecognized transport: {0}
WSWS2014E: 'EAR filename' parameter is missing or empty.
WSWS2015E: 'props' parameter is missing.
WSWS2016I: Loading EAR file: {0}
WSWS2017I: Found EJB Module: {0}
WSWS2018I: Finished processing EAR file {0}.
WSWS2019I: Enabling EJB Module {0}...
WSWS2020I: Finished enabling EJB Module {0}...
WSWS2021I: Skipping EJB Module {0} since it contains no Web services.
WSWS2022I: Skipping {0} router module for EJB Module {1} since it already contains a router for this transport.
WSWS2023I: Skipping {0} router for EJB Module {1} due to 'skip' property.
WSWS2024I: Adding {0} router for EJB Module {1}.
WSWS2025I: Router module name: {0}
WSWS2026I: Context root: {0}
WSWS2027I: Listener Input Port: {0}
WSWS2028I: Destination type: {0}
WSWS2029I: Enter {0} router name for EJB Module {1} [{2}]:
WSWS2030I: Enter {0} context root for EJB Module {1} [{2}]:
WSWS2031I: Enter {0} listener input port name for EJB Module {1} [{2}]:
WSWS2032E: Invalid destination type specified: {0}
WSWS2033I: Enter {0} destination type for EJB Module {1} [{2}]:
WSWS2034I: Usage syntax: endptEnabler [options] [trace options] [
WSWS2035E: Error loading the JSR 109 deployment descriptor {0} for EJB Module {1}.
WSWS2036I: Saving EAR file {0}...
WSWS2037I: Finished saving the EAR file.
WSWS2038I: Trace has been enabled for the following components: {0}
WSWS2039I: Trace data will be logged in file: {0}
WSWS2040W: EJB jar {0} contains protected EJBs,
yet the -enableHttpRouterSecurity option was not specified, so the resulting
HTTP router module, {1}, will not include security information.
WSWS2041W: The -enableHttpRouterSecurity option was specified,
yet the EJB jar {0} contains at least one unprotected EJB or the existing
security information is incomplete. Therefore, security information will not be added
to the {1} HTTP router module.
WSWS2042E: Listener input port {0} has already been configured for JMS router module {1}.
WSWS3000I: WSDL2Java emitter
Usage: WSDL2Java [options] WSDL-URI
Important Options:
-r, -role
WSWS3001I: Info:
Extended Options:
-U, -user
WSWS3002I: Java2WSDL emitter
Usage: Java2WSDL [options] class-of-portType
Options:
-location
WSWS3003I: Info:
Extended Options:
-wrapped
WSWS3004W: Warning: The -location was not set, the value "{0}" is used instead.
WSWS3005W: Warning: The -server-side option must have an argument that is Bean or EJB. Defaulting to Bean.
WSWS3006W: Warning: The argument of the -transport option must be "jms" or "http". The default setting ("http") will be used.
WSWS3007E: Error: The {0} operation of {1} has an output element. This output element is removed and the operation is changed to one-way.
WSWS3008E: Error: The {0} operation of {1} has a fault element. The faults are removed and the operation is changed to one-way.
WSWS3009I: Info: Loading Class {0}
WSWS3010I: Info: Generating {0} {1}
WSWS3011E: Invalid destination type "{0}" specified within a JMS endpoint URL.
WSWS3012E: Invalid property "{0}" encountered in JMS endpoint URL.
WSWS3013E: The JMS endpoint URL is missing one or more of the following required properties: connectionFactory, destination, targetService
WSWS3014E: Error creating InitialContext: {0}
WSWS3015E: Caught NamingException: {0}
WSWS3016E: Caught JMSException: {0}
WSWS3017E: Linked Exception: {0}
WSWS3018E: Caught exception during request processing: {0}
WSWS3019E: Caught WebServicesFault: {0}
WSWS3020E: Error getting server engine.
WSWS3021E: The required "{0}" property was not present in the inbound JMS request message.
WSWS3022E: Unrecognized inbound JMS request message type.
WSWS3023E: Two-way requests are not supported for topic destinations.
WSWS3024E: Root part containing SOAP envelope not found. contentId = {0}
WSWS3025E: Error: Could not locate a parameter named {0} for {1}.
WSWS3026E: Error: The argument of the -voidReturn option must be "oneway" or "twoway".
WSWS3027E: Error: The {0} SAX event is not supported by SOAP.
WSWS3028E: Error: A _Helper class was not found for {0}.
WSWS3029W: Warning: The xml construct named {0} cannot be mapped to a java type. The construct will be mapped to javax.xml.soap.SOAPElement.
WSWS3030E: Error: An internal error occurred while trying to locate the target method. Debug:{0}
WSWS3031E: Error: Serialization cannot occur for {0}. There are no registered type mappings.
WSWS3032I: Info: Attempt to get a secure socket factory using KeyStore: {0} and TrustStore: {1}, or Cryptographic token in: {2}
WSWS3033E: Error: Deserialization cannot occur for {0}.
WSWS3034E: Error: The OperationDesc for {0} was not matched to a method of {1}. Debug:{2}
WSWS3035E: Error: {0}.{1} threw RuntimeException.
WSWS3036I: Replacing response message with SOAP Fault. Original Response Message: {0}
WSWS3037E: Error: Serialization cannot occur for {0}.
WSWS3038E: Error: Deserialization cannot occur for {0}. There are no registered type mappings.
WSWS3039E: Error: Resource has been deleted.
WSWS3040E: Error: Malformed arrayType value ''{0}''
WSWS3041E: Error: Bad authentication type (I can only handle "Basic").
WSWS3042E: Error: Invalid boolean (found {0}).
WSWS3043E: Error: Unexpected characters in a calendar value: {0}
WSWS3044E: Error: Bad character or insufficient number of characters in hex string.
WSWS3045E: Error: Invalid date: {0}
WSWS3046E: Error: Invalid date/time: {0}
WSWS3047E: Error: Cannot deserialize element {1} of bean {0}.
WSWS3048E: Error: Class ''{0}'' cannot be specified as a Handler class.
WSWS3049E: Error: A bad Holder class was encountered: {0}
WSWS3050E: Error: Explicit array length is not a valid integer ''{0}''.
WSWS3051E: Error: No ''name'' attribute was specified in an undeployment element.
WSWS3052E: Error: Bad envelope namespace: {0}
WSWS3053E: Error: An attempt was made to construct a Name object with an invalid string: {0}
WSWS3054E: Error: An attempt was made to construct a NCName object with an invalid string: {0}
WSWS3055E: Error: An attempt was made to construct a NegativeInteger object with an invalid string: {0}
WSWS3056E: Error: An attempt was made to construct a NMToken object with an invalid string: {0}
WSWS3057E: Error: An attempt was made to construct a NonNegativeInteger object with an invalid string: {0}
WSWS3058E: Error: An attempt was made to construct a NonPositiveInteger object with an invalid string: {0}
WSWS3059E: Error: Malformed offset attribute ''{0}''.
WSWS3060E: Error: Invalid Parameter mode {0}.
WSWS3061E: Error: Malformed position attribute ''{0}''.
WSWS3062E: Error: portName should not be null.
WSWS3063E: Error: An attempt was made to construct a PosInteger object with an invalid string: {0}
WSWS3064E: Error: Cannot handle non-GET, non-POST request.
WSWS3065E: Error: Unrecognized -scope: {0}. Ignoring it.
WSWS3066E: Error: Expected ''envelope'' but found {0}
WSWS3067E: Error: Invalid time: {0}
WSWS3068E: Error: Invalid timezone: {0}
WSWS3069E: Error: Found languageSpecificType namespace ''{0}'', expected ''{1}''
WSWS3070E: Error: An attempt was made to construct an UnsignedByte object with an invalid string: {0}
WSWS3071E: Error: An attempt was made to construct an UnsignedShort object with an invalid string: {0}
WSWS3072E: Error: An attempt was made to construct an UnsignedInt object with an invalid string: {0}
WSWS3073E: Error: An attempt was made to construct an UnsignedLong object with an invalid string: {0}
WSWS3074E: Error: Cannot add a second body to a soap envelope.
WSWS3075E: Error: User ''{0}'' not authenticated (unknown user).
WSWS3076E: Error: User ''{0}'' not authenticated.
WSWS3077E: Error: User ''{0}'' not authorized to ''{1}''
WSWS3078E: Error: Cannot convert {0} to bytes.
WSWS3079E: Error: Cannot convert form {0} to String.
WSWS3080E: Error: Could not convert {0} to bean field ''{1}'', type {2}
WSWS3081E: Error: Could not convert value to int.
WSWS3082E: Error: Cannot serialize null arrays.
WSWS3083E: Error: getURL failed to correctly process URL; protocol not supported.
WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize.
WSWS3085E: Error: Cannot invoke Call with null namespace URI for method {0}
WSWS3086E: Error: Cannot serialize a {0} with the ArraySerializer.
WSWS3087E: Error: Cannot serialize non-Elements with an ElementSerializer.
WSWS3088E: Error: Cannot serialize a raw object with the SimpleSerializer.
WSWS3089E: Error: Cannot set location URI: {0}
WSWS3090E: Error: Unable to tunnel through {0}:{1}. Proxy returns "{2}"
WSWS3091E: Error: Changing admin password.
WSWS3092E: Error: SOAPElement.setAlternateContent called when a child element is present.
WSWS3093E: Error: Could not create Call object in AdminClient.
WSWS3094E: Error: WSDDPort couldn't construct provider!
WSWS3095E: Error: Connection closed.
WSWS3096E: Error: Duplicate file name: {0}.
Hint: you may have mapped two namespaces with elements of the same name to the same package name.
WSWS3097E: Error: Emitter failure. All input parts must be listed in the parameterOrder attribute of {0}
WSWS3098E: Error: Emitter failure. Cannot find endpoint address in port {0} in service {1}
WSWS3099E: Error: Emitter failure. Invalid endpoint address in port {0} in service {1}: {2}
WSWS3100E: Error: Emitter failure. No binding found for port {0}
WSWS3101E: Error: Emitter failure. No binding entry found for {0}
WSWS3102E: Error: Emitter failure. No portType entry found for {0}
WSWS3103E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document.
Hint: make sure
WSWS3104E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document {1}.
Hint: make sure
WSWS3105E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document.
Hint: make sure
WSWS3106E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document {1}.
Hint: make sure
WSWS3107E: Error: Generic Error.
WSWS3108E: Error: Error: {0}
WSWS3109E: Error: Error invoking Web service operation: {0}
WSWS3110E: Error: Error processing ''{0}''
WSWS3111E: Error: Error determining if {0} already exists. Will not generate this file.
WSWS3112E: Error: Generating WebServicesFault due to missing SOAPAction.
WSWS3113E: Error: Cannot add a second header to a soap envelope.
WSWS3114E: Error: Internal error.
WSWS3115E: Error: Configuration file directory ''{0}'' is not readable.
WSWS3116W: Warn: PERFORMANCE ALERT: The following message is re-parsed: {0}
WSWS3117E: Error: Invalid container type (expected "ejb", "web", "client" or "none"), defaulting to "none".
WSWS3118E: Error: Invalid role (expected "develop-client", "deploy-client", "develop-server", or "deploy-server"), defaulting to "develop-client".
WSWS3119E: Error: Invalid option combination: -role develop-server and -container client or -container none are invalid. The -container will be defaulted to "web".
WSWS3120E: Error: Configuration is missing.
WSWS3121I: Info: {0} is a oneway operation.
WSWS3122E: Error: Could not find service {0} referenced in URI {1}
WSWS3123E: Error: Javaclass {0} specified for handler {1} must implement {2} OR {3}. The handler will be skipped.
WSWS3124E: Error: Invalid -genJava option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
WSWS3125E: Error: Invalid -genXML option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
WSWS3126E: Error: Could not get a secure socket factory from the following SSL Configuration: {0}.
WSWS3127E: Error: Invalid WSDD element ''{0}'' (wanted ''{1}'').
WSWS3128E: Error: Could not make envelope from bytes.
WSWS3129E: Error: Only interfaces may be used for the proxy Class argument of the Service.getPort method.
WSWS3130E: Error: Only interfaces which extend java.rmi.Remote may be used for the proxy Class argument of the Service.getPort method.
WSWS3131E: Error: Must specify a password for AdminClient.
WSWS3132E: Error: No target service was found.
WSWS3133E: Error: Need to specify a user for authorization.
WSWS3134E: Error: Remote administrator access is not allowed.
WSWS3135E: Error: Body not found.
WSWS3136E: Error: No deserializer defined for array type {0}
WSWS3137E: Error: No deserialization context to use in SOAPElement.convertToObject().
WSWS3138E: Error: No custom elements allowed at top level until after the
WSWS3139E: Error: No deserializer for {0}
WSWS3140E: Error: Deserializing parameter ''{0}'': could not find deserializer for type {1}
WSWS3141E: Error: Could not get DOM document: XML was "{0}"
WSWS3142E: Error: Could not find Web services engine.
WSWS3143W: Warning: Expected instance of ''EngineConfiguration'' in environment.
WSWS3144E: Error: Cannot locate handler: {0}
WSWS3145E: Error: No HandlerProvider ''handlerClass'' option was specified.
WSWS3146E: Error: No handlers in {0} ''{1}''
WSWS3147E: Error: no {0} header!
WSWS3148E: Error: Processing instructions are not allowed within SOAP messages.
WSWS3149E: Error: {0}: {1} is not a map.
WSWS3150E: Error: No provider type matches QName ''{0}''
WSWS3151E: Error: No operation name specified.
WSWS3152E: Error: Cannot find operation: {0} - none defined
WSWS3153E: Error: Cannot find operation: {0}
WSWS3154E: Error: No ''{0}'' option was configured for the service ''{1}''
WSWS3155E: Error: {0} not found as an input part OR an output part.
WSWS3156E: Error: Cannot find port: {0}
WSWS3157E: Error: Cannot find portType: {0}
WSWS3158E: Error: No request message in MessageContext?
WSWS3159E: Error: No serializer found for class {0} in registry {1}
WSWS3160E: Error: Cannot find service: {0}
WSWS3161E: Error: No service has been defined.
WSWS3162E: Error: No service object defined for this Call object.
WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is {0}
WSWS3164E: Error: No security provider in MessageContext.
WSWS3165E: Error: No HTTP SOAPAction property in context.
WSWS3166E: Error: No client transport named ''{0}'' found.
WSWS3167E: Error: No transport mapping for protocol: {0}
WSWS3168E: Error: No mapped schema type for {0}
WSWS3169E: Error: Component requires a type attribute.
WSWS3170E: Error: Must include type attribute for Handler deployment!
WSWS3171E: Error: No type QName for mapping!
WSWS3172E: Error: User ''{0}'' not authorized to ''{1}''
WSWS3173E: Error: Did not understand "MustUnderstand" header(s):{0}
WSWS3174E: Error: No value field for RPCParam to use. {0}
WSWS3175E: Error: {0} is null.
WSWS3176E: Error: AdminClient did not initialize correctly: ''call'' is null!
WSWS3177E: Error: Null namespace URI specified.
WSWS3178E: Error: null parent.
WSWS3179E: Error: Null provider type passed to WSDDProvider.
WSWS3180E: Error: Null response message.
WSWS3181E: Error: Odd number of digits in hex string.
WSWS3182E: Error: Only one Body element allowed in SOAPEnvelope.
WSWS3183E: Error: Only one Header element allowed in SOAPEnvelope.
WSWS3184E: Error: Number of parameters passed in ({0}) doesn''t match the number of IN/INOUT parameters ({1}) from the addParameter() calls.
WSWS3185I: Info: Parsing XML file: {0}
WSWS3186E: Error: Error in parsing: {0}
WSWS3187E: Error: Processing file {0}
WSWS3188I: Info: {0} quitting.
WSWS3189E: Error: Administration service requested to quit, quitting.
WSWS3190E: Error: Unable to bind to port {0}. Did not start SimpleServerEngine.
WSWS3191I: Info: Configuration file read-only so engine configuration changes will not be saved.
WSWS3192E: Error: return code: {0}
{1}.
WSWS3193E: Error: Problem with servlet engine /WEB-INF directory
WSWS3194E: Error: Problem with servlet engine config file: {0}
WSWS3195W: Warn: Unable to load/create servlet engine config file, attempting internal default (from jar).
WSWS3196E: Error: Problem with servlet engine config file (loading from jar).
WSWS3197I: Info: {0} starting up on port {1}.
WSWS3198E: Error: Type/Element attribute on Part ''{0}'' is not set.
WSWS3199E: Error: Unexpected end of stream.
WSWS3200E: Error: Unknown host - could not verify admininistrator access.
WSWS3201E: Error: Where {0} looks like:
WSWS3202E: Error: Error processing WSDL document: {0} {1}
WSWS3203E: Error: Missing WSDL document in Service.getPort.
WSWS3204E: Error: {0} already exists.
WSWS3205E: Error: Type {0} is referenced but not defined.
WSWS3206E: Error: Cannot find EJB at JNDI location {0}
WSWS3207E: Error: Cannot create InitialContext.
WSWS3208E: Error: The definition of {0} results in a loop.
WSWS3209E: Error: Bad property. The value for {0} should be of type {1}, but it is of type {2}.
WSWS3210E: Error: Null property name specified.
WSWS3211E: Error: Null property value specified.
WSWS3212E: Error: Property name {0} not supported.
WSWS3213E: Error: Null getter method specified.
WSWS3214E: Error: Null setter method specified.
WSWS3215E: Error: Null public instance field specified.
WSWS3216E: Error: Null java class specified in TypeMappingImpl.isRegistered method.
WSWS3217E: Error: Null qualified name specified in TypeMappingImpl.isRegistered method.
WSWS3218E: Error: Null serializer factory specified in the TypeMappingImpl.register method.
WSWS3219E: Error: Error: Message part {0} of operation or fault {1} is specified as a type and the soap:body use of binding "{2}" is literal. This WSDL is not currently supported.
WSWS3220E: Error: Error: Empty or missing service name.
WSWS3221E: Error: Bean attribute {0} is of type {1}, which is not a simple type.
WSWS3222E: Error: Attribute is of type {0}, which is not a simple type.
WSWS3223E: Error: Exception caught while constructing handler {0}: {1}
WSWS3224I: Info: No disk access, using memory only.
WSWS3225E: Error: No DeserializerFactory for {0}
WSWS3226E: Error: Null FieldDesc specified.
WSWS3227E: Error: Exception:
WSWS3228E: Error: Exception: {0}
WSWS3229E: Error: ConfigurationException:
WSWS3230E: Error: ParserConfigurationException:
WSWS3231E: Error: SAXException:
WSWS3232E: Error: java.net.UnknownHostException:
WSWS3233E: Error: javax.mail.MessagingException:
WSWS3234E: Error: java.io.IOException:
WSWS3235E: Error: java.io.IOException: {0}
WSWS3236E: Error: IllegalAccessException:
WSWS3237E: Error: IllegalArgumentException:
WSWS3238E: Error: IllegalArgumentException: {0}
WSWS3239E: Error: InvocationTargetException:
WSWS3240E: Error: InstantiationException:
WSWS3241E: Error: MalformedURLException:
WSWS3242E: Error: WebServicesFault:
WSWS3243I: Info: Mapping Exception to WebServicesFault.
WSWS3244I: Info: Mapping Exception to WebServicesFault: {0}
WSWS3245E: Error: WSDL2Java emitter timed out (this often means the WSDL at the specified URL is inaccessible)!
WSWS3246E: Error: SOAPFault.addDetail called when a detail is present.
WSWS3247E: Error: No endpoint.
WSWS3248E: Error: Unsupported attachment type "{0}" only supporting "{1}".
WSWS3249E: Error: This attachment implementation accepts only SOAPPart objects as the root part.
WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.
WSWS3251E: Error: Stream closed.
WSWS3252E: Error: End of stream encountered before final boundary marker.
WSWS3253E: Error: maxCached value is bad: {0}
WSWS3254E: Error: Reset and mark not supported!
WSWS3255E: Error: input buffer is null.
WSWS3256E: Error: Offset is negative: {0}
WSWS3257E: Error: Length: {0}
WSWS3258E: Error: Write beyond buffer.
WSWS3259E: Error: Error reading data stream: {0}
WSWS3260E: Error: File for data handler does not exist: {0}
WSWS3261E: Error: Error in MIME data stream, start boundary not found, expected: {0}.
WSWS3262E: Error: Error in parsing mime data stream: {0}.
WSWS3263E: Error: No support for attachments.
WSWS3264E: Error: No content.
WSWS3265E: Error: No engine configuration file - aborting.
WSWS3266E: Error: The element "{0}" is an attachment with sub elements which is not supported.
WSWS3267E: Error: Error: Missing type resolution for element {2}, in WSDL message part {0} of operation {1}.
WSWS3268E: Error: The soap:operation for binding operation {0} must have a "use" attribute.
WSWS3269E: Error: Default type mapping cannot be modified.
WSWS3270E: Error: Type mapping cannot be modified via delegate.
WSWS3271E: Error: Invalid TypeMapping specified: wrong type or null.
WSWS3272E: Error: Default type mapping from secondary type mapping registry is already in use.
WSWS3273E: Error: There is no stub implementation for the interface:
WSWS3274E: Error: {0}: {1} is not a vector.
WSWS3275E: Error: Invalid parameter mode byte ({0}) passed to getModeAsString().
WSWS3276E: Error: Marking streams not supported.
WSWS3277E: Error: No such operation ''{0}''
WSWS3278E: Error: Attempt to set implementation class on a ServiceDesc which has already been configured.
WSWS3279E: Error: Unable to create JavaBean of type {0}. Missing default constructor? Error was: {1}.
WSWS3280E: Error: The value of -soapAction must be DEFAULT, NONE or OPERATION.
WSWS3281E: Error: Tried to invoke method {0} with arguments {1}. The arguments do not match the signature.
WSWS3282I: Info: Generating {0}.
WSWS3283E: Error: The value of -style must be DOCUMENT or RPC.
WSWS3284E: Error: Could not find class ''{0}'' for the service.
WSWS3285E: Error: Could not find class ''{0}'' for the service ''{1}''.
WSWS3286E: Error: The
WSWS3287E: Error: The
WSWS3288E: Error: The wsdl URI has already been specified as, {0}. It cannot be specified again as {1}.
WSWS3289E: Error: The wsdl URI was not specified.
WSWS3290E: Error: Unrecognized {0}: ''{1}''
WSWS3291E: Error: The class {0} is not a bean class and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
WSWS3292W: Warning: The class {0} is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
WSWS3293E: Error: The class {0} does not contain a default constructor, which is a requirement for a bean class. The class cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
WSWS3294E: Error: The XML Schema type ''{0}'' is not currently supported.
WSWS3295E: Error: Message part {0} of operation or fault {1} has no element or type attribute.
WSWS3296E: Error: The value of {0} for attachment format must be {1};
WSWS3297E: Error: DIME Type length is {0} which exceeds maximum {0}
WSWS3298E: Error: DIME ID length is {0} which exceeds maximum {1}.
WSWS3299E: Error: Max chunk size "{0}" needs to be greater than one.
WSWS3300E: Error: Max chunk size "{0}" exceeds 32 bits.
WSWS3301E: Error: Each DIME Stream must be read fully or closed in succession.
WSWS3302E: Error: DIME stream data not padded correctly.
WSWS3303E: Error: Received "{0}" bytes to read.
WSWS3304E: Error: Received "{0}" as an offset.
WSWS3305E: Error: Array to read is null.
WSWS3306E: Error: Array size of {0} to read {1} at offset {2} is too small.
WSWS3307E: Error: End of physical stream detected when more DIME chunks expected.
WSWS3308E: Error: End of physical stream detected when {0} more bytes expected.
WSWS3309E: Error: There are no more DIME chunks expected!
WSWS3310E: Error: DIME header less than {0} bytes.
WSWS3311E: Error: DIME version received "{0}" greater than current supported version "{1}".
WSWS3312E: Error: DIME option length "{0}" is greater stream length.
WSWS3313E: Error: DIME stream closed during options padding.
WSWS3314E: Error: DIME stream closed getting ID length.
WSWS3315E: Error: DIME stream closed getting ID padding.
WSWS3316E: Error: DIME stream closed getting type.
WSWS3317E: Error: DIME stream closed getting type padding.
WSWS3318E: Error: DIME stream received bad type "{0}".
WSWS3319E: Error: A holder could not be found or constructed for the OUT parameter {0} of method {1}.
WSWS3320E: Error: Illegal argument passed to ParameterDesc.setJavaType. The java type {0} does not match the mode {1}.
WSWS3321E: Error: Invalid normalizedString value.
WSWS3322E: Error: Invalid token value.
WSWS3323E: Internal Error occurred while build the property descriptors for {0}.
WSWS3324E: Error: Problems encountered trying to write schema for {0}
WSWS3325E: Error: Error looking for parameter names in bytecode: input does not appear to be a valid class file.
WSWS3326E: Error: Error looking for paramter names in bytecode: unexpected end of file.
WSWS3327E: Error: Error looking for paramter names in bytecode: unexpected bytes in file.
WSWS3328E: Error: The class {0} extends non-bean class {1}. An xml schema anyType will be used to define {0} in the wsdl file.
WSWS3329E: Error: The XML Schema type ''{0}'' is not valid in the Schema version ''{1}''.
WSWS3330I: Info: {0} already exists, WSDL2Java will not overwrite it.
WSWS3331E: Error: Invalid gYearMonth: {0}
WSWS3332E: Error: Invalid gYear: {0}
WSWS3333E: Error: Invalid gMonth: {0}
WSWS3334E: Error: Invalid gDay: {0}
WSWS3335E: Error: Invalid gMonthDay: {0}
WSWS3336E: Error: Invalid duration: must contain a P.
WSWS3337E: Error: Serializer class {0} does not implement SimpleValueSerializer, which is necessary for attributes.
WSWS3338E: Error: JIMI is necessary to use java.awt.Image attachments (http://java.sun.com/products/jimi/).
WSWS3339E: Error: javax.xml.transform.Source implementation not supported: {0}.
WSWS3340E: Error: The OperationDesc for {0} was not syncronized to a method of {1}.
WSWS3341E: Error: No service class was found.
WSWS3342E: Error: Cannot handle {0}, can only handle JPEG image types.
WSWS3343W: Warning: Factory {0} Ignored: missing required method: {1}.
WSWS3344W: Warning: Factory {0} Ignored: invoke method failed: {1}.
WSWS3345E: Error: Unable to locate a valid EngineConfigurationFactory.
WSWS3346E: Error: Factory {0} Ignored: unable to load/resolve class.
WSWS3347E: Error: classname attribute is missing.
WSWS3348E: Error: qname attribute is missing.
WSWS3349E: Error: Element {0} is referenced but not defined.
WSWS3350E: Error: Missing type or ref attribute for node ''{0}''
WSWS3351E: Error: Unable to deploy typemapping: {0}
WSWS3352E: Error: Couldn''t find a matching Java operation for WSDD operation "{0}" ({1} args).
WSWS3353E: Error: Method style for message-based service wasn't one we recognized.
WSWS3354E: Error: Method ''{0}'' does not match any of the valid signatures for message-style service methods.
WSWS3355E: Error: unmatchedOp=Binding operation has no corresponding portType operation: name = {0}, input name = {1}, output name = {2}
WSWS3356E: Error: Couldn't find an appropriate operation for XML QName {0}
WSWS3357E: Error: while trying to deserialize operation {0}, an element named {1} was encountered.
However, this element does not match any of the expected parameters for this operation.
Here is the list of expected parameters:
{2}
WSWS3358E: Error: ERROR: Unable to match binding fault "{0}" from binding {2}, operation "{1}", to a PortType fault.
WSWS3359E: Error: Fault is missing a name= attribute in operation "{0}", in binding {1}.
WSWS3360E: Error: ERROR: Missing
WSWS3361E: Error: Found instance data for {0} in the soap:body instead of the soap:header.
WSWS3362E: Error: Didn''t find specified return QName {0}
WSWS3363E: Error: The value of the -use option must be LITERAL or ENCODED.
WSWS3364E: Error: Invalid class provided for -extraClasses option: {0}
WSWS3365E: Error: Cannot invoke a oneway call when the call has a return type.
WSWS3366E: Error: The operation must be specified.
WSWS3367E: Error: Failure priming the MessageContext object for operation invocation: {0}
WSWS3368E: Error: The deserialization event {0} for ({1}) was unexpected in {2}.
WSWS3369E: Error: The builder {0} does not have a SOAPElement to build.
WSWS3370E: Error: Only one SOAPEnvelope is allowed in a SOAPFactory.
WSWS3371E: Error: Cannot invoke addChildElement on a {0} object.
WSWS3372E: Error: Cannot add a {0} child element to a {1} object.
WSWS3373E: Error: Cannot invoke addTextNode on a {0} object.
WSWS3374E: Error: Cannot replace SOAPElement's attributes.
WSWS3375E: Error: Cannot replace SOAPElement's MappingScope.
WSWS3376E: Error: Don't know how to convert alternate content of class {0}.
WSWS3377E: Error: Multiple elements have the name ({0}):{1}.
WSWS3378E: Error: Can't set alternate content on a SOAPElement that already has alternate content.
WSWS3379E: Error: Prefix {0} is undefined.
WSWS3380E: Error: An attempt was made to modify a read-only MappingScope.
WSWS3381E: Error: Circular loop encountered while processing MappingScope.
WSWS3382E: Error: An unqualified namespace cannot have a prefix. Prefix is {0}.
WSWS3383E: Error: Illegal use of xmlns prefix encountered: {0}
WSWS3384E: Error: Admin process failed.
WSWS3385E: Error: The onStartChild method of {0} did not return a processor.
WSWS3386E: Error: Tried to push a null processor.
WSWS3387E: Error: An attempt was made to serialize a null object. This should have been handled in the serialize() method.
WSWS3388E: Error: Exception generated while rewinding request handlers during fault processing: exception ignored, processing halted.
WSWS3389E: Error: JAXRPC Handler Class {0} not found/loaded, ignored.
WSWS3390E: Error: Load of class {0} failed unexpectedly.
WSWS3391W: Warn: {0}.handleRequest returned false and failed to set response message.
WSWS3392E: Error: Unexpected: Unable to create response message on behalf of handler.
WSWS3393E: Error: {0}.handlerRequest should not throw javax.xml.rpc.soap.SOAPFaultException on client-side.
WSWS3394E: Internal Error: attempted to put {0} into pool of {1}.
WSWS3395E: Error: {0}.{1} threw RuntimeException.
WSWS3396E: Error: Handler {0}: Protected state violation. (JSR 109, Web services for J2EE, V1.0, 6.2.2.2).
WSWS3397E: Error: JSR-109 requires that Service.getHandlerRegistry() throw an UnsupportedOperationException in a managed container.
WSWS3398E: Error: JSR-109 requires that Service.getTypeMappingRegistry() throw an UnsupportedOperationException in a managed container.
WSWS3399E: Error: {0} ''{1}'' didn't implement ''{2}''.
WSWS3400I: Info: unexpected exception.
WSWS3401E: Error: RequestMessage missing on MessageContext.
WSWS3402E: Error: INTERNAL: ResponseMessage missing on MessageContext.
WSWS3403E: Error: Unexpected Life Cycle State: current="{0}", expected="{1}".
WSWS3404E: Error: Unexpected: SubSet({0}, {1}, {2}): acting as empty set.
WSWS3405I: Info: Ignoring exception thrown by {0}.
WSWS3406E: Unexpected exception caught while sending reply message: {0}
WSWS3407E: Invalid protocol for JMS URL string: {0}
WSWS3408E: A valid URL string can not be formed from the properties contained in the JMSURLParser object.
Linked exception: {0}
WSWS3409E: Internal Error: Client/Server mode not set for soap port.
WSWS3410E: Invalid value specified for the {0} property.
WSWS3411E: Request timeout exceeded.
WSWS3412E: A JMS reply message was received which did not correlate with the JMS request message.
WSWS3413E: The JMS reply message was not of the correct JMS message type.
WSWS3414E: Style DOCUMENT, Use LITERAL, and Wrapped do not allow operation {0} to be overloaded.
WSWS3415E: Buffer size <= 0
WSWS3416E: Stream closed.
WSWS3417W: Response set in MessageContext for a one-way message. Reponse will be ignored.
WSWS3418E: Error: Exception generated during handler fault processing.
WSWS3419I: From target realm: {0} .
WSWS3420I: HTTP Basic Authentication information has been received.
WSWS3421E: No HTTP Basic Authentication Information has been received from the prompt.
WSWS3422E: Error while running class ''{0}''.
WSWS3423W: Binding {0} has already been generated and will not be re-generated.
WSWS3424W: One-way operations were requested for methods returning 'void', but operation ''{0}'' has been declared to throw a fault, so it will be converted into a two-way operation.
WSWS3425E: No binding generator was found for binding type ''{0}''.
WSWS3426I: Found a binding generator for binding type ''{0}''.
WSWS3427W: A binding specific location property was not specified for the requested {0} binding. The default location ''{1}'' will be used.
WSWS3428W: The generic -location option should not be used when more than one binding type has been requested.
WSWS3429I: Binding-specific properties are {0}
WSWS3432E: The ''{0}'' property is required, but was not specified.
WSWS3433E: One or more errors occurred while validating the input properties.
WSWS3434E: There is no binding defined for {0} RequestSender.
WSWS3435E: There is no deployment descriptor defined for {0} RequestSender.
WSWS3436E: Could not find WSDL file ''{0}'' within the EAR.
WSWS3437E: Caught {0} while trying to read WSDL file ''{1}'': {2}
WSWS3438E: No WSDL services were found for namespace ''{0}''.
WSWS3439E: The ClassLoader parameter was passed in as null.
WSWS3440E: The port name and service ref name are both null.
WSWS3441E: The endpoint address URL is missing.
WSWS3442E: Error: Could not get a secure socket factory with the SSL settings of JSSE.
WSWS3443I: Info: HTTP Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
WSWS3444I: Info: HTTPS Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
WSWS3445I: Info: SSL configuration is from {0}.
WSWS3446I: Info: Response from Proxy for HTTP CONNECT: {0}.
WSWS3447E: Mixture of different settings for 'style/use' within a WSDL binding is NOT supported. Inconsistent values for the "{0}" binding are: {1}={2} and {3}={4}
WSWS3448E: The requested WSDL document is not displayed because there are no SOAP ports present in the requested WSDL. Use the /extwsdl query to access the full WSDL document.
WSWS3523E: The serialization engine detected an element nesting greater than 100 elements. This exceeds the limit of the serialization engine. This problem was found while serializing an object of class: {0}
WSWS3548W: Warning: WSDL2Java could not discover a suitable StubWriter. The default SOAP StubWriter will be used.
WSWS3549E: Error: WSDL2Java could not discover a suitable StubWriter for {0}.
WSWS3553E: Error: The value of -MIMEstyle must be AXIS or WSDL11.
WSWS3554E: The ''{0}'' property is invalid unless -bindingTypes http (or no bindingTypes) is also specified.
WSWS3555E: The ''{0}'' property is invalid unless -bindingTypes jms is also specified.
WSWS3556E: The ''{0}'' property is invalid unless -bindingTypes ejb is also specified.
WSWS4048E: WSWS4048E the JMS URL prefix {0} is not correctly formatted. It must start with jms:/[queue|topic]?, and the destination and connectionFactory must not contain java:comp.
WSWS4049E: WSWS4049E the EJB URL suffix {0} is not correctly formatted. It must have the form
WSWS5001E: {0} is null.
WSWS5002E: Input parameter {0} was passed in as null, but {1} has not been called.
WSWS5003E: Caught {0} while retrieving method ''{1}'' from class ''{2}'': {3}
WSWS5004E: Caught {0} while invoking method ''{1}'' on class ''{2}'': {3}
WSWS5005E: {0} is not an interface.
WSWS5006E: Class {0} is not an instance of EJBHome or EJBLocalHome.
WSWS5007E: Caught {0} while attempting to locate the following JNDI name: {1}
{2}
WSWS5008E: Caught {0} while trying to obtain an InitialContext object.
WSWS5009E: Caught {0} while attempting to create protocol-specific Call object: {1}
WSWS5010E: Error: Cannot find port: {0}
WSWS5011E: Method {0} is not supported in a managed environment.
WSWS5012E: Error loading generated Stub class ''{0}'': {1}
WSWS5013E: No constructor with the signature {0} was found for generated Stub class ''{1}'': {2}
WSWS5014E: Error instantiating generated Stub class ''{0}'': {1}
WSWS5015E: No WSDL definition was found at URI: {0}
WSWS5016E: The WSDL definition located at URI ''{0}'' did not contain Service ''{1}''.
WSWS5017E: Error reading WSDL definition located at URI: {0}
WSWS5018E: Caught {0} while trying to invoke method ''{1}'' from class ''{2}'': {3}
WSWS5019E: Error obtaining Service for port ''{0}'': {1}
WSWS5020E: Error obtaining Stub class ''{0}'': {1}
WSWS5021E: Error obtaining port ''{0}'': {1}
WSWS5022E: Error while trying to create extension for parent type ''{0}'' and element type ''{1}''.
WSWS5023E: Invalid protocol in endpoint location URI: {0}
WSWS5024E: Missing '=' in query string within endpoint location URI: {0}
WSWS5025E: Invalid attribute name: {0}
WSWS5026E: Internal error: duplicate shadow registry.
WSWS5027E: Invalid property name for Call object: ''{0}''
WSWS5028E: Caught {0} while trying to close a transport: {1}
WSWS5029E: Caught {0} while processing a method invocation: {1}
WSWS5030E: Invalid method: {0}
WSWS5031E: Invalid Service Endpoint Interface: ''{0}''. No WSDL definition available.
WSWS5032E: Invalid Service Endpoint Interface: ''{0}''. No default port available.
WSWS5033E: Cannot create a dynamic proxy without a WSDL definition.
WSWS5034E: Cannot create a dynamic proxy without a port QName.
WSWS5035E: Port ''{0}'' does not exist.
WSWS5036E: No WSDL definition is available.
WSWS5037E: The {0} is not supported by the {1} class.
WSWS5038I: not used
WSWS5039I: not used
WSWS5040I: not used
WSWS5041E: Error getting protocol from endpoint location URI: ''{0}''
WSWS5042E: Invalid protocol found in WSDL endpoint location URI. Expected {0}, but found {1}.
WSWS5043E: The Service class ''{0}'' does not implement the ''{1}'' interface.
WSWS5044E: The required constructor was not found for the generated Service class: ''{0}''
WSWS5045E: {0}: empty port name found in WSDL port names array.
WSWS5046E: Caught {0} getting EJB class name from endpoint location URI ''{1}'': {2}
WSWS5047E: Caught {0} getting properties from endpoint location URI ''{1}'': {2}
WSWS5048E: The {0} property is missing from endpoint location URI ''{1}''.
WSWS5049E: Caught an unexpected exception while trying to instantiate a target object of class ''{0}'': {1}
WSWS5050E: Caught {0} while trying to initialize target object of class ''{1}'': {2}
WSWS5051E: Caught {0} while trying to load target object class ''{1}'': {2}
WSWS5052E: Caught {0} getting implementation class name from endpoint location URI ''{1}'': {2}
WSWS5053E: Caught {0} while trying to get method ''{1}'' on target class ''{2}'': {3}
WSWS5054E: Caught {0} while trying to invoke method ''{1}'' on target class ''{2}'': {3}
WSWS5055E: Could not find a Service for namespace ''{0}''.
WSWS5056E: Cannot create a dynamic proxy due to exception: {0}
WSWS5057E: There is no PortType in the WSDL defintion for the specified service endpoint interface: ''{0}''.
WSWS5058E: Invalid Service Endpoint Interface: ''{0}'' is not an interface.
Explanation:
If there is more than one service in the WSDL file the Client Deployment Descriptor must specify a QName of which service to use.
User Response:
Modify the Client Deployment Descriptor to add a
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A warning was issued w/the deployment descriptor listed.
User Response:
Correct the problem with the deployment descriptor.
Explanation:
An error was issued w/the deployment descriptor listed.
User Response:
Correct the error with the deployment descriptor.
Explanation:
A fatal error was issued w/the deployment descriptor listed.
User Response:
Correct the fatal error with the deployment descriptor.
Explanation:
WebSphere unable to locate WebContainer during Web services startup.
User Response:
Correct problems with WebSphere startup.
Explanation:
Invalid value for scope.
User Response:
Correct scope in binding file to one of 'Request', 'Application', or 'Session'.
Explanation:
A configuration file (was-webservices.xml) defines a provider which specifies a javaclass that cannot be loaded.
User Response:
Determine cause of failure to load the specified Java class, and fix.
Explanation:
Either a servlet with name matching servlet-link was not found for a port component, or the Web application is not a Servlet.
User Response:
Use valid servlet name in servlet-link field and verify that the Web application is a servlet.
Explanation:
The port-component-name values must be unique.
User Response:
Use unique port-component-names.
Explanation:
The JAX-RPC mapping Deployment Descriptor specified in the Web services Client Deployment Descriptor can not be read.
User Response:
Make sure that the file name specified in the Web service Client Deployment Descriptor references a valid JAX-RPC Mapping file in the module.
Explanation:
Error in handler configuration. Handler ignored may cause unexpected results.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Error in handler configuration. Handler ignored, may cause unexpected results.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Error in configuration.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
No (zero) services found to deploy.
User Response:
Specify services to be deployed.
Explanation:
Unexpected type of client reference in namespace.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The reference was not found in the namespace.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The reference for the module is not valid.
User Response:
Service references for this type of module must be contained in a '
Explanation:
Resource not visible to class and system class loaders.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Resource cannot be loaded by class and system class loaders.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The MBean could not be registered.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The Web services EJB Collaborator could not be initialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The MetaData service could not be found.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The service reference could not be bound.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The service reference could not be bound into the namespace.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The service reference could not be bound into the namespace.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A configuration file (was-webservices.xml) defines a handle which specifies a javaclass that cannot be loaded.
User Response:
Determine cause of failure to load the specified Java class, and fix.
Explanation:
The port component binding is not required, but certain functionality will not be available without it.
User Response:
No action required.
Explanation:
Exception caught, dumping context info.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The required JAX-RPC mapping Deployment Descriptor named in the Web services Deployment Descriptor can not be found in this module.
User Response:
Make sure that the file name specified in the Web service Deployment Descriptor references an existing file in the module.
Explanation:
The service name could not be changed from the default name generated in the ServiceLocator because a setter for the ServiceName could not be found.
User Response:
Regenerate the client side artifacts including the ServiceLocator class with the WebSphere emitters.
Explanation:
This file required in order to make this type of module available as a Web service.
User Response:
Ensure the module in the application contains the indicated bindings file.
Explanation:
The file is not required, but certain functionality will not be available without it.
User Response:
No action required.
Explanation:
The Web service description binding is not required, but certain functionality will not be available without it.
User Response:
No action required.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The router module is missing from the application.
User Response:
Fix the application by running endpointEnabler tool.
Explanation:
One or more of the values for the defaultMappings information in the client bindings file can not be found in the WSDL file.
User Response:
Verify and correct the defaultMappings information in the client bindings file.
Explanation:
The port type of a preferred port (DefaultMapping) was not defined in the corresponding WSDL file for this service.
User Response:
Fix the bindings file.
Explanation:
The service reference in the deployment descriptor identifies this WSDL file, but it could not be opened.
User Response:
Ensure the WSDL file is in the module and is properly identified in the deployment descriptor.
Explanation:
No service references were found in the deployment descriptor.
User Response:
Fix the deployment descriptor.
Explanation:
None.
User Response:
None.
Explanation:
The requested trace data will be logged to the standard output stream.
User Response:
None.
Explanation:
These are instructions for enabler tools.
User Response:
Follow instructions as requested.
Explanation:
The endpoint enabler tool is making a backup copy of the EAR file.
User Response:
None.
Explanation:
Standard IBM banner displayed by enabler tools.
User Response:
None.
Explanation:
Standard IBM banner displayed by enabler tools.
User Response:
None.
Explanation:
These are instructions for enabler tools.
User Response:
Follow instructions as requested.
Explanation:
Standard IBM Copyright.
User Response:
None.
Explanation:
The '-transport' parameter was specified on the command line but the associated value was not specified.
User Response:
Specify a value for the '-transport' parameter and re-try the command.
Explanation:
The '-properties' parameter was specified on the command line but the associated properties filename was not specified.
User Response:
Specify a properties filename for the '-properties' parameter and re-try the command.
Explanation:
The endpoint enabler is reading properties from the specified file.
User Response:
None.
Explanation:
The specified command-line parameter was encountered but is not a recognized as a valid command-line parameter.
User Response:
Correct the command and re-try.
Explanation:
Properties being used by the endpoint enabler.
User Response:
None.
Explanation:
An unrecognized transport type was specified for the '-transport' command-line parameter or within a
User Response:
Ensure that only valid transport types are used on the command line and within the properties file.
Explanation:
A null value or empty string was passed for the 'EAR filename' parameter to the EndpointEnabler.enableEarFile method.
User Response:
Ensure that a valid EAR filename is passed.
Explanation:
A null value was passed for the 'props' parameter to the EndpointEnabler.enableEarFile method.
User Response:
Ensure that a valid Properties object is passed for the 'props' parameter.
Explanation:
The endpoint enabler has started loading the specified EAR file into memory.
User Response:
None.
Explanation:
The endpoint enabler recognized the specified EJB jar within the EAR file, and is processing the EJB jar.
User Response:
None.
Explanation:
The endpoint enabler tool has finished processing the specified EAR file.
User Response:
None.
Explanation:
The endpoint enabler has started to process the specified EJB jar module.
User Response:
None.
Explanation:
The endpoint enabler has finished processing the specified EJB jar module.
User Response:
None.
Explanation:
The specified EJB Module does not contain a JSR109 deployment descriptor.
Therefore, it must not contain any Web services and does not need to be enabled.
User Response:
None.
Explanation:
The specified EJB Module already contains a router module for the specified transport.
User Response:
None.
Explanation:
The indicated router module will not be added to the EAR since the user specified a 'skip' property for the indicated EJB Module.
User Response:
None.
Explanation:
The endpoint enabler is adding a router module for the specified transport.
User Response:
None.
Explanation:
The endpoint enabler is displaying the name of the new router module.
User Response:
None.
Explanation:
The endpoint enabler is displaying the context root for the new router module.
User Response:
None.
Explanation:
The endpoint enabler is displaying the listener port for the new router module.
User Response:
None.
Explanation:
The endpoint enabler is displaying the destination type for the new router module.
User Response:
None.
Explanation:
Requesting a name for the router module.
User Response:
Please follow instructions as requested.
Explanation:
Requesting the context root for a router module.
User Response:
Please follow instructions as requested.
Explanation:
Requesting the listener port name for a router module.
User Response:
Please follow instructions as requested.
Explanation:
Valid destination types include 'queue' and 'topic'.
User Response:
Correct the destination type and re-try.
Explanation:
Requesting the destination type for the router module.
User Response:
Please follow instructions as requested.
Explanation:
This message explains how to invoke the endptEnabler command-line tool.
User Response:
None.
Explanation:
The enabler tool was unable to read the specified deployment descriptor file. This is possibly due to some unexpected or invalid structure within.
User Response:
Please check for and correct any errors the reported file may contain.
Explanation:
The endpoint enabler tool is saving the EAR file to disk.
User Response:
None.
Explanation:
The endpoint enabler tool has finished saving the EAR file to disk.
User Response:
None.
Explanation:
This message tells the user that tracing has been enabled for one or more components.
User Response:
None.
Explanation:
The requested trace data will be logged into the specified file.
User Response:
None.
Explanation:
This is simply a warning which indicates security information will not be
added to the HTTP router module since the -enableHttpRouterSecurity option was not specified on the command line.
If you would like the HTTP router module to be protected, simply specify the -enableHttpRouterSecurity option.
User Response:
None.
Explanation:
This is simply a warning which indicates that
security information will not be added to the HTTP router module since the EJB jar does not
contain complete security information.
If you would like the HTTP router module to be protected, make sure that the EJB jar
contains complete security information.
User Response:
None.
Explanation:
A listener input port that is configured with a Queue should not be used with more than one JMS router module. The web service implementations contained within a particular EJB jar module share a listener input port (and hence they also share the associated Queue), but the listener input port should not be shared with another EJB jar module.
User Response:
Create a new listener input port and associate it with one of the JMS router modules.
Explanation:
These are the options to WSDL2Java.
User Response:
Use the specified options when invoking WSDL2Java.
Explanation:
These are the extended options to WSDL2Java.
User Response:
These are advanced options that users should not generally use.
Explanation:
These are the options to Java2WSDL.
User Response:
Use the specified options when invoking Java2WSDL.
Explanation:
These are the extended options to Java2WSDL.
User Response:
These are advanced options that users should not generally use.
Explanation:
The -location option is a required option.
User Response:
Please specify the -location option.
Explanation:
The -server-side option is incorrect.
User Response:
Please specify the correct -server-side option.
Explanation:
The -transport option is incorrect.
User Response:
Please specify the correct option.
Explanation:
This pre-existing operation has an output element. It is removed.
User Response:
None.
Explanation:
This pre-existing operation has a fault element. It is removed.
User Response:
None.
Explanation:
Loading specified class.
User Response:
None.
Explanation:
Generating indicated construct.
User Response:
None.
Explanation:
A JMS endpoint URL must specify either 'queue' or 'topic' as the destination type.
User Response:
Correct the JMS endpoint URL and re-try.
Explanation:
A JMS endpoint URL string contained an unrecognized property.
User Response:
Correct the JMS endpoint URL and re-try.
Explanation:
A JMS endpoint URL string must contain the following properties: connectionFactory, destination, targetService.
These properties are used to describe the destination queue or topic and target service.
User Response:
Correct the JMS endpoint URL and re-try.
Explanation:
An error occurred while trying to create a JNDI InitialContext object.
User Response:
Use the detailed information in the original error message to determine the problem.
Explanation:
The specified error occurred during a JNDI 'lookup' operation.
User Response:
Ensure that the JNDI name is correct.
Explanation:
A JMS operation resulted in the specified JMSException.
User Response:
Use the detailed information in the original error message to determine how to correct the problem.
Explanation:
None.
User Response:
None.
Explanation:
The specified exception occurred while a request was being processed.
User Response:
Use the detailed information in the original error message to determine how to correct the problem.
Explanation:
The specified WebServicesFault exception occurred.
User Response:
Use the detailed information in the original error message to determine how to correct the problem.
Explanation:
The Web services message-driven bean listener was unable to retrieve a configured server engine during its initialization.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic.
This is an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The Web services JMS listener received a JMS message that was not a TextMessage or a BytesMessage. The JMS listener supports only these two JMS message types.
User Response:
Ensure that the JMS sender uses the correct JMS message type.
Explanation:
A two-way request/response was invoked for a topic destination,
but only one-way requests are supported when using a topic.
User Response:
Ensure that any services which use topic destinations contain only one-way operations.
This means that within the WSDL file, the operation does not contain an 'output' message.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Suspect a bad mapping file supplied to WSDL2Java.
User Response:
Correct your mapping file.
Explanation:
The -voidReturn option is incorrect.
User Response:
Please specify the correct option.
Explanation:
The message is not a legal SOAP message.
User Response:
Contact party that sent this message.
Explanation:
The _Helper class is needed for proper serialization or deserialization. Serialization or deserialization may fail.
User Response:
Ensure that the _Helper class was properly emitted by WSDL2Java and deployed correctly.
Explanation:
Some xml constructs cannot be mapped to java types.
User Response:
The application code will need to use the SOAPElement methods to construct and analyze the data.
Explanation:
An internal error occurred. Possibly due to an error in the deployment infornation.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The indicated object cannot be serialized.
User Response:
Make sure that a proper serializer is registered.
Explanation:
Used either a KeyStore/TrustStore pair or a cryptographic token to get a secure socket factory
User Response:
None.
Explanation:
The indicated type cannot be deserialized.
User Response:
Make sure that a proper deserializer is registered.
Explanation:
Internal error caused by improper startup code.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original exception.
User Response:
Correct Handler code to eliminate RuntimeException.
Explanation:
Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original response message.
User Response:
Correct Handler code to eliminate RuntimeException.
Explanation:
The indicated object cannot be serialized.
User Response:
Make sure that a proper serializer is registered.
Explanation:
The indicated type cannot be deserialized.
User Response:
Make sure that a proper deserializer is registered.
Explanation:
Trying to access a deleted memory managed data source.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The arrayType attribute in the soap message is invalid.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Only Basic authentication is supported with the SimpleServerEngine.
User Response:
You should not be using the SimpleServerEngine.
Explanation:
A boolean value in a soap message must be '0', '1', 'true' or 'false'.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A calendar value in a soap message was invalid.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A character in a hex string was invalid.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A bad date value was found in a soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A bad date/time value was found in a soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The specified bean does not have a property that matches the element. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An attempt was made to deploy the indicated class as a Handler class. However it does nt extend the Handler class.
User Response:
Correct your deployment information. CMSG0002
Explanation:
An attempt was made to use the specified class as a Holder. However the class does not extend the Holder interface.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The soap message contains an array that has a non-integer array length. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This is normally the result of an internal error in the deployment software.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The envelope element of the soap message has an incorrect namespace. The message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The offset attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal exception of the WSDL2Java emitter.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The position attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The portName argument to the service.getCalls method must be a recognized port name.
User Response:
Ensure that the argument to the service.getCalls method is appropriate.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
SimpleServerEngine does not understand the request.
User Response:
Don't use the SimpleServerEngine.
Explanation:
The argument of the scope option must be Request, Application, or Session.
User Response:
Use the proper -scope option when invoking WSDL2Java.
Explanation:
A soap message does not contain an envelope element.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A bad time value was found in a soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A bad timezone was found in a soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A problem has occurred in the deployment software.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is caused by an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This error could be the result of an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
User cannot be authenticated.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
User cannot be authenticated.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
User is not authorized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error: The soap message cannot be converted into bytes.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error: The soap message cannot be converted into a String.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The indictated value could not be assigned to the bean field. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Tool option error. See other messages.
User Response:
Fix the URL.
Explanation:
This message normally indicates that the soap message is invalid. The engine was expecting a simple value when it encountered a child element. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The indicated class cannot be serialized with the array serializer.
User Response:
Suspect a problem with the deployment information.
Explanation:
The element serializer can only be used to serialize org.w3c.dom.Element objects.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The SimpleSerializer cannot be used to serialize a non-registered object.
User Response:
Make sure your this class is registered with an appropriate type.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Can't make the appropriate tunnel.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Changed passwords on AdminClient.
User Response:
AdminClient is not fully supported.
Explanation:
The SAAJ model is being used incorrectly. Please contact the Web services team. if this problem is occurring in the runtime.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
Don't use AdminClient.
Explanation:
Internal Error with deployment software.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The connection is closed. The remote service call cannot be made.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
WSDL2Java issues this message if an different qnames result in the creation of the same java file.
User Response:
Fix your wsdl or use the NStoPkg options to differentiate the classes.
Explanation:
The parameter order attribute in the wsdl is incorrect.
User Response:
Fix your wsdl.
Explanation:
The endpoint address cannot be found.
User Response:
Fix your wsdl.
Explanation:
The endpoint address is invalid.
User Response:
Fix your wsdl.
Explanation:
Specify a binding on the service wsdl port.
User Response:
Fix your wsdl
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The binding must be defined if referenced.
User Response:
Fix the WSDL.
Explanation:
The binding must be defined if referenced.
User Response:
Fix the WSDL.
Explanation:
The portType must be be defined if referenced.
User Response:
Fix the WSDL.
Explanation:
The portType must be defined if referenced.
User Response:
Fix the WSDL.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Problem occurred invoking remote Web service.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Admin error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This error could be the result of an invalid soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The specified directory cannot be read.
User Response:
Fix your configuration.
Explanation:
Non performant serialization encountered.
User Response:
Examine code and make appropriate changes.
Explanation:
The -container option of WSDL2Java is wrong.
User Response:
Fix the option setting.
Explanation:
The -role option of WSDL2Java is wrong.
User Response:
Fix the option setting.
Explanation:
The Web service always runs in a web or ejb container.
User Response:
Fix the options and rerun WSDL2Java.
Explanation:
This is most likely due to a previous error with the Web services deployment descriptor.
User Response:
Review the log for previous errors.
Explanation:
informational message.
User Response:
no action required.
Explanation:
The specified service could not be found.
User Response:
Check the name of the service specified by the client and the deployment of that service on the server.
Explanation:
A configuration file (was-webservices.xml) defines a handle javaclass that does not implement the expected interface.
User Response:
Specify javaclass that implements the expected interface.
Explanation:
The -genJava option of WSDL2Java is wrong.
User Response:
Correct the option setting.
Explanation:
The -genXML option of WSDL2Java is wrong.
User Response:
Correct the option setting.
Explanation:
Could not get a secure socket factory.
User Response:
Correct your SSL configuration.
Explanation:
Error occurred during deployment. This is probably an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This could possibly due to a deserialization error. Look for other errors.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The getPort method requires a proxy interface.
User Response:
Correct the invocation of the getPort method.
Explanation:
The proxy Class argument must be an interface that extends java.rmi.Remote.
User Response:
Fix the invocation of the getPort method.
Explanation:
A password must be supplied.
User Response:
AdminClient is not fully supported.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
No user was found to authorize.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Cannot administor remotely.
User Response:
The Admin class is not fully supported.
Explanation:
A body was expected in the soap envelope, but was not found. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The array of the indicated component type could not be deserialized.
User Response:
This problem may be due to invalid deployment information.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
tag.
Explanation:
The soap message is invalid and cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally this is the result of bad client or server deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Nornally this is the result of a bad soap message or invalid server deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Probably an Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Invalid configuration data.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error with deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Missing information in deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Missing handlers in deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Header missing in soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The soap message is invalid and cannot be deserialized due to presences of processing instructions.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The object cannot be serialized by the MapSerializer. This is probably the result of an internal deployment error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Deployment information is not complete. This is probably the result of an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The WSDL does not define any operations in the portType.
User Response:
This is an internal error or deployment error.
Explanation:
The WDSL binding did not specify the operation.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The indicated option was not found.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The parameter order attribute must reference a message part.
User Response:
Correct the WSDL.
Explanation:
The specified port could not be found by Service.getPort.
User Response:
Correct the invocation of Service.getPort.
Explanation:
The deployed wsdl is missing the portType.
User Response:
Correct the deployed wsdl.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Usually this indicates a internal error with the deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Make sure a security provider is configured.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The indicated array component type cannot be serialized. Make sure this type is registered.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The component of the vector cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Missing deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Missing deployment information in the type mapping registry.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Handler did not understand mustUnderstand headers.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Exception.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Processing cannot continue because the indicated item is null.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
AdminClient is not fully supported.
Explanation:
Namespace argument must be specified.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Tried to call SAAJ setParent with a null argument. This may be the result of an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Missing deployment information. This may be the result of an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The HexBinary object cannot be constructed.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The soap message contains multiple soap bodies inside the envelope. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The soap message contains multiple soap headers inside the envelope. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The number of parameters does not match the expected number of parameters.
User Response:
This could be a DII or internal error.
Explanation:
informational message.
User Response:
no action required.
Explanation:
Problem occurred deserializing the soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
AdminClient error processing the indicated file.
User Response:
AdminClient is not fully supported.
Explanation:
informational message.
User Response:
no action required.
Explanation:
Admin quitting.
User Response:
Admin class is not fully supported.
Explanation:
Internal Error.
User Response:
SimpleServerEngine not fully supported.
Explanation:
informational message.
User Response:
no action required.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
/WEB-INF may not be accessible.
User Response:
Correct problem with WEB-INF directory.
Explanation:
config file may not be accessible.
User Response:
Correct problem with servlet engine config file.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
no action required.
Explanation:
Configuration error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
informational message.
User Response:
no action required.
Explanation:
The WSDL part must specify the type or element attribute.
User Response:
Correct the deployed wsdl.
Explanation:
Internal Error or problem with input soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Unknown host encountered by Admin tool.
User Response:
The Admin tool is not fully supported.
Explanation:
Admin tool error.
User Response:
Admin tool is not fully supported.
Explanation:
Normally an error with the deployed wsdl detected during service creation.
User Response:
Correct the deployed wsdl.
Explanation:
A WSDL document is needed if you want to use Service.getPort.
User Response:
Correct your deployment information.
Explanation:
Internal Error in the WSDL2Java SymbolTable.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Your wsdl references types or elements that are not defined.
User Response:
Correct your wsdl.
Explanation:
There may be a problem with your JNDI configuration.
User Response:
Correct your JNDI configuration.
Explanation:
An InitialContext was not created.
User Response:
Inspect other errors to determine why InitialContext was not created.
Explanation:
Found recursive definition of the indicated type or element.
User Response:
Correct your wsdl.
Explanation:
A bad propery detected on the Call or MessageContext. This could be caused by an internal error.
User Response:
Fix the property.
Explanation:
A bad property was detected. This could be caused by an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A null property value was specified. This could be caused by an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An unsupported property is being used.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This is normally due to an internal error associated with the serialization engine.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This is normally due to an internal error associated with the deserialization engine.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This is normally due to an internal error with the serialization engine.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The isRegistered method requires a non-null java class. This error could be the result of an internal problem.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The isRegistered method requires a non-null qname. This error could be the result of an intrnal problem.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This error normally suggests a problem with the deployment software.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The WSDL contains unsupported MIME constructs.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The WSDL service name is wrong.
User Response:
Correct the WSDL.
Explanation:
Attributes must be simple types.
User Response:
Correct the WSDL.
Explanation:
Attributes must be simple types.
User Response:
Correct the WSDL.
Explanation:
Problem creating JAXRPC Handler.
User Response:
Review reasons for thrown exception.
Explanation:
informational message
User Response:
No action required.
Explanation:
This normally indicates a problem with the deployed type mapping registry.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Exception.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Used for various fatal exceptions. See other messages.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Used for various excpeptions. See other messages.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally indicates an internal error has occurred.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Indicates that an error has occurred while configuring the xml parser.
User Response:
Correct the parser configuration.
Explanation:
Indicates that a SAX Exception has occurred. Normally the exception is due to a problem configuring the parser.
User Response:
Correct the parser configuration.
Explanation:
Normally indicates that an internal error has occurred.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normlly indicates a problem with a MIME message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Normally an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This may be issued during overloaded message processing.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
This error may occur during overloaded method processing.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
A problem occured invoking the indicated target.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
This error may indicate a problem with MIME attachments.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Malformed URL Exception occurred in the SimpleServerEngine.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
A WebServicesFault has occurred.
User Response:
See other messages for more detailed information.
Explanation:
informational message. See other messages for details about why the fault was issued.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
informational message. See other messages for details about why the fault was issued.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
Normally indicates that the WSDL is not accessible.
User Response:
Make sure the WSDL is accessible.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
See other messages for more details.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
Indicates that an unsupported attachment type was encountered.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Interal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Possibly an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Tried to access a closed stream.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Data Handler has no content.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Possibly an internal error.
User Response:
Make sure your engine configuration is correct.
Explanation:
Child elements were not anticipated in the soap message. The soap message cannot be deserialized.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Your WSDL may be bad.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Probably an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The type mapping cannot be modified after registration has occurred.
User Response:
Please correct your code.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Invalid TypeMapping registration.
User Response:
Please correct your code.
Explanation:
Cannot change default type mapping after registration.
User Response:
Please correct your code.
Explanation:
You cannot call this getPort method because there is no stub implementation of the interface.
User Response:
Please change your code.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This may be a symptom of a Web service deployment problem.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Exception.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Make sure that the JavaBean has a default constructor.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A bad argument was specified for -soapAction.
User Response:
Use the correct Java2WSDL -soapAction option.
Explanation:
Suspect a problem with the Web service deployment or the soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Informational message indicating which java classes are generated by WSDL2Java.
User Response:
no action required.
Explanation:
The -style option of Java2WSDL is incorrect.
User Response:
Use a correct -style option.
Explanation:
Suspect a Web service deployment error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Suspect a Web service deployment error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Only one class file may be specified for Java2WSDL.
User Response:
Correct your invocation of Java2WSDL.
Explanation:
A class file must be specified for Java2WSDL.
User Response:
Correct your invocation of Java2WSDL.
Explanation:
The WSDL file can only be specified once for WSDL2Java.
User Response:
Correct your invocation of WSDL2Java.
Explanation:
The WSDL URI must be specified for WSDL2Java.
User Response:
Correct your invocation of WSDL2Java.
Explanation:
Inappropriate value for the enumeration.
User Response:
Please correct your code.
Explanation:
Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
Explanation:
Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
Explanation:
Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
Explanation:
WSDL2Java does not support this XML Schema type.
User Response:
Correct your wsdl.
Explanation:
Each message part must have an element or type attribute which locates the schema element/type.
User Response:
Correct your wsdl.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Suspect a problem with deploying this Web service.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Suspect a problem with deploying this Web service. Probably an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The NormalizedString object could not be set due to an invalid value.
User Response:
Correct the normalizedString value.
Explanation:
The Token object could not be set due to an invalid value.
User Response:
Correct the token value.
Explanation:
Internal Error.
User Response:
Make sure the indicate class complies with JAX-RPC.
Explanation:
Could not write the schema for the indicated class. This is probably due to an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
You probably specified an invalid class to Java2WSDL.
User Response:
Correct the indicated class.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
Explanation:
WSDL2Java error.
User Response:
Please correct your wsdl.
Explanation:
WSDL2Java informational message.
User Response:
No action required.
Explanation:
Error occurred while constructing a YearMonth object.
User Response:
Use a correct value.
Explanation:
Error occurred while constructing a Year object.
User Response:
Use a correct value.
Explanation:
Error occurred while constructing a Month object.
User Response:
Use a correct value.
Explanation:
Error occurred while constructing a Day object.
User Response:
Use a correct value.
Explanation:
Error occurred while constructing a MonthDay object.
User Response:
Use a correct value.
Explanation:
Error occurred while constructing a Duration object.
User Response:
Use a correct value.
Explanation:
This serializer cannot be used to serialize attributes.
User Response:
Please correct your deployed type mappings.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An attempt was made to use the SourceDataHandlerSerializer to serialize a non-SourceStream object.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error. This error usually indicates that information was missing in the PortDesc/WSDDPort in regards to the definition of the Web service operations. The engine attempts to deduce the missing information, which may result in this particular error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Correct your factory implementation.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
Invoke method failed.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
Missing factory implementation.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Cannot load the indicated factory.
User Response:
Make sure that the factory can be loaded.
Explanation:
WSDD Deployment information is missing. This may be due to an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
WSDD Deployment information is missing. This may be due to an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
WSDL2Java error indicating that an element is referenced but no definition was found.
User Response:
Please correct your wsdl.
Explanation:
A type or ref attribute is used to reference a type or element.
User Response:
Please correct your wsdl.
Explanation:
This may be due to a deployment problems.
User Response:
Make sure that the indicated class can be found and loaded.
Explanation:
Normally this indicates a problem with the missing or incorrect deployment information.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error. This is an unsupported api.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error. This is an unsupported api.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An invalid binding operation was encountered in the wsdl.
User Response:
Please correct the wsdl.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The SOAP request message received by the service does not match the WSDL definition.
User Response:
Make sure that the SOAP message sent to the service matches the WSDL definition.
Explanation:
The binding fault must have a corresponding portType fault.
User Response:
Please correct the wsdl
Explanation:
The binding fault must have a name.
User Response:
Please correct the wsdl.
Explanation:
The binding fault must have a appropriate
User Response:
Please correct the wsdl.
Explanation:
The soap message is incorrect.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The response soap message is incorrect.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The -use option of Java2WSDL is incorrect.
User Response:
Correct the -use option.
Explanation:
The -extraClasses option of Java2WSDL is incorrect.
User Response:
Correct the -extraClasses option.
Explanation:
A method was encountered that has a return type, but Java2WSDL was invoked in a mode that assumes that the method is one way.
User Response:
Correct the class.
Explanation:
Probably an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Probably an internal error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This can be caused by an internal error or a bad input soap message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Cannot add a child SOAPElement to the indicated object.
User Response:
Correct your code.
Explanation:
Cannot add the indicated child element.
User Response:
Correct your code.
Explanation:
Cannot add a Text node to the indicated object.
User Response:
Correct your code.
Explanation:
Cannot call setAttributes after the SOAPElement has attributes.
User Response:
Correct your code.
Explanation:
Cannot call setMappingScope after the SOAPElement has a MappingScope.
User Response:
Correct your code.
Explanation:
This is an unrecognized alternate content type.
User Response:
Correct your code.
Explanation:
Expecting only one child element of the given qname.
User Response:
Correct your code.
Explanation:
An attempt was made to set alternate content on a SOAPElement that already has alternate content.
User Response:
Make sure you remove the existing alternate content before replacing it.
Explanation:
The indicated prefix does not have a corresponding namespace uri.
User Response:
Correct your code or soap message.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The soap message has an illegal xmlns prefix.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Admin tool failed.
User Response:
The Admin tool is not fully supported.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An exception was thrown during handler fault processing.
User Response:
Inspect your handlers.
Explanation:
The indicated class could not be found and/or loaded.
User Response:
Determine why the class was not found or loaded.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Warning.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
Warning.
User Response:
This exception is unexpected. The cause is not immediately known.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Tried to illegally manipulate xml.
User Response:
Correct your handler.
Explanation:
Cannot call this method in a managed container.
User Response:
Correct your handler.
Explanation:
Cannot call this method in a managed container.
User Response:
Correct your handler.
Explanation:
Deployment error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Probably an internal problem.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Informational Message.
User Response:
No action required.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The protocol for a JMS URL string should be "jms:"
User Response:
Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.
Explanation:
The set of properties currently contained within the JMSURLParser object cannot form a valid JMS-style URL string.
User Response:
Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The value supplied for the specified property was not correct.
User Response:
Make sure that you use the correct value for the specified property.
Explanation:
A request did not complete within the specified timeout period.
User Response:
Make sure that your server is active and is able to process requests within the allotted time.
Explanation:
The JMS correlation id in the reply message did not match the JMS message id in the request message.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The JMS reply message should be of type javax.jms.BytesMessage, but it was a different type.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
To allow overloaded operations would cause duplicate xsi types of the same name.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal Error.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Runtime set a response message onto the MessageContext for a one-way message.
User Response:
Correct JAXRPC Handler logic.
Explanation:
An exception was thrown during handler fault processing.
User Response:
Inspect your handlers.
Explanation:
informational message.
User Response:
no action required.
Explanation:
informational message.
User Response:
no action required.
Explanation:
Runtime does not receive any HTTP Basic Authentication information after the prompt
User Response:
Make sure userid and password are both entered at the prompt.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
An unsupported binding type was requested.
User Response:
Ensure that only valid binding types are requested.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
You have requested more than one binding type with the -bindingTypes option, but you have specified a single endpoint location URI with the -location option. When requesting multiple binding types, specify binding-specific endpoint location URI values for each of the requested binding types by using the
User Response:
Specify multiple endpoint location URI values with the -properties option.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
The ClassLoader parameter is required for the method to function properly, but a null value was passed in.
User Response:
Ensure that a non-null value is passed in for the ClassLoader parameter.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A Web services request was made which involves the JMS transport, but the request does not include a valid endpoint address URL.
User Response:
Make sure that the request contains a valid endpoint address URL. If this request was invoked within the Web Services Gateway, make sure the proper configuration has been done.
Explanation:
Could not get a secure socket factory using the SSL settings of JSSE
User Response:
Verify your JSSE SSL setting if you intend to use JSSE SSL setting for the SSL configuration.
Explanation:
Configured HTTP proxy information.
User Response:
None.
Explanation:
Configured HTTPS proxy information.
User Response:
None.
Explanation:
Specified SSL configuration. It can be by a java property file, a SSL configuration alias, or the JSSE SSL settings.
User Response:
None.
Explanation:
HTTP response from Proxy for the HTTP CONNECT request
User Response:
None.
Explanation:
WS-I mandates that the 'style/use' must be the same for 'input/outputs' and 'faults' in any one binding. For more details visit WS-I at: http://www.ws-i.org/
User Response:
Modify your WSDL document to make the 'style/use' settings for 'inputs, outputs' and/or 'faults' consistent.
Explanation:
Appending "/wsdl" to a service URL is a request to retrieve a WSDL document that contains SOAP ports for the HTTP or JMS transports. If there are no such ports, this error is displayed instead of the WSDL document.
User Response:
Modify the query to obtain the extended wsdl or contact the Web service owner.
Explanation:
An attempt was made to serialize a message with too deep a nesting. This could be due to a linked list with too many nodes. This problem could also be due to an attempt to serialize a graph containing looped references.
User Response:
Please correct the data being serialized.
Explanation:
Internal discovery problem, perhaps with classloader.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
Internal discovery problem, perhaps with classloader. Can't continue.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The -MIMEstyle option of Java2WSDL is incorrect.
User Response:
Use a correct -MIMEstyle option.
Explanation:
When property is specified, the corresponding property must also be specified.
User Response:
Respecify the property using bindningTypes http.
Explanation:
When property is specified, the corresponding property must also be specified.
User Response:
Respecify the property using bindningTypes jms.
Explanation:
When propertie is specified, the corresponding property must also be specified.
User Response:
Respecify the property using bindingTypes ejb.
Explanation:
Incorrect user input for JMS url prefix.
User Response:
Provide correct input.
Explanation:
Incorrect user input for EJB URL suffix
User Response:
Provide correct input.
Explanation:
A null value was passed for the specified parameter, and this is not valid for this particular operation.
User Response:
Make sure that a non-null value is passed in for the specified parameter.
Explanation:
If a null argument is going to be passed in, then the specified method should be called to set the type of each argument.
User Response:
Make sure that you first call the appropriate method to set the argument types, or make sure that you do not pass a null argument to the 'invoke' method.
Explanation:
The specified exception was caught while attempting to retrieve the specified method from the specified class.
User Response:
Make sure that the specified EJB class contains the appropriate methods.
Explanation:
The specified exception was caught while attempting to invoke the specified method from the specified class.
User Response:
Make sure that the specified EJB class contains the appropriate methods.
Explanation:
The specified parameter should be an interface, not a class.
User Response:
Make sure that the parameter is passed in as an interface.
Explanation:
The specified class name should refer to a valid EJBHome class, but the class is not an instance of EJBHome or EJBLocalHome.
User Response:
A class name which refers to a valid EJBHome or EJBLocalHome class should be passed in.
Explanation:
An error was encountered while attempting to do a JNDI lookup of the specified JNDI name.
User Response:
Make sure that the correct JNDI lookup name is specified within the endpoint location URI.
Explanation:
The specified exception was caught while trying to create an InitialContext object which would be used to perform JNDI lookup operations.
User Response:
Use the exception details to determine how to resolve the problem.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The specified port could not be found by Service.getPort.
User Response:
Correct the invocation of Service.getPort.
Explanation:
Within the managed J2EE environment, the Service.getTypeMappingRegistry and Service.getHandlerRegistry methods are not supported. They may only be called within the unmanaged JSR-101 client environment.
User Response:
Make sure that you do not call these methods when the client application is running within the J2EE managed environment.
Explanation:
The specified exception was thrown while a generated Stub class was being loaded.
User Response:
Make sure that the specified Stub class exists and is available to be loaded.
Explanation:
The specified generated Stub class should have a constructor with the specified signature.
User Response:
Make sure that the proper Stub class is being used.
Explanation:
The specified exception was thrown when a new instance of the generated Stub class was being created.
User Response:
Make sure that the proper generated Stub class is being used.
Explanation:
The ServiceFactory.createService method was unable to find a WSDL definition at the specified location.
User Response:
Make sure that the WSDL document is available and that the WSDL location is correct.
Explanation:
The specified WSDL definition was located, but it did not contain the specified Service.
User Response:
Make sure that the WSDL document contains the correct Service and that you are using the correct Service name.
Explanation:
The specified WSDL document was either not found, or contained an error.
User Response:
Make sure that the WSDL document exists and that it is correct.
Explanation:
An exception was thrown while attempting to invoke a method from the specified class.
User Response:
Make sure that the specified EJB class contains the appropriate methods.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The specified exception was thrown while an attempt was made to obtain an instance of the generated Stub class.
User Response:
Make sure that the generated Stub class is available to be loaded.
Explanation:
An error occurred while trying to obtain the Stub for the specified port.
User Response:
Make sure that the generated Stub object exists and that the port name is correct.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The specified endpoint location URI contains an incorrect protocol.
User Response:
Correct the endpoint location URI.
Explanation:
An error was found while parsing the specified endpoint location URI.
User Response:
Correct the endpoint location URI.
Explanation:
The caller tried to set or get the value for the specified attribute from an ExtensibilityElement, but the attribute name is not a valid name.
User Response:
Make sure that a valid attribute is used.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An attempt was made to set or get the specified property on a Call object, but the property name is not valid.
User Response:
Make sure that you are using a valid property name.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
An exception was thrown during the processing of a method request.
User Response:
Use the detailed information from the error message to determine the cause of the error.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
When calling Service.getPort(Class), the WSDL definition is required but was not available.
User Response:
Make sure the WSDL definition is available.
Explanation:
When calling Service.getPort(Class), a default port is required but was not available.
User Response:
Make sure that a default port exists for the Service Endpoint Interface.
Explanation:
If a generated Stub class is not found, then a dynamic proxy will be created, but the WSDL definition is required.
User Response:
Make sure the WSDL definition is available.
Explanation:
If a generated Stub class is not found, then a dynamic proxy will be created, but a non-null port name is required.
User Response:
Make sure that a non-null port name is passed in.
Explanation:
The specified port is not a valid port for the service.
User Response:
Correct the port name.
Explanation:
The Service.getPorts() method cannot return the list of ports unless the WSDL definition is available.
User Response:
Make sure the WSDL definition is available.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
None.
User Response:
None.
Explanation:
An error occurred while trying to obtain the protocol the specified endpoint location URI.
User Response:
Make sure the endpoint location URI is correct.
Explanation:
An unexpected protocol value was found in the endpoint location URI.
User Response:
None.
Explanation:
A JAX-RPC Service class must implement the specified interface in order to conform to the JAX-RPC specification. In this situation, the Web services runtime loaded a class assumed to be a valid Service class, but it does not implement the expected interface.
User Response:
Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool.
Explanation:
See error message.
User Response:
Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
The EJB class name could not be obtained from the specified endpoint location URI.
User Response:
Correct the endpoint location URI.
Explanation:
An occurred while parsing the properties contained in the specified endpoint location URI.
User Response:
Correct the endpoint location URI.
Explanation:
A required property was missing from the endpoint location URI.
User Response:
Correct the endpoint location URI.
Explanation:
Unable create an instance of the specified implementation class.
User Response:
Refer to the exception in the original error message to determine how to resolve the problem.
Explanation:
Unable to initialize an instance of the specified implementation class.
User Response:
Refer to the exception in the original error message to determine how to resolve the problem.
Explanation:
Unable to load the specified implementation class.
User Response:
Make sure that the implementation class is available to be loaded.
Explanation:
Unable to obtain the implementation class name from the endpoint location URI.
User Response:
Correct the endpoint location URI.
Explanation:
Unable to find the specified method on the specified implementation class.
User Response:
Make sure that the correct implementation class is being used.
Explanation:
An exception was thrown while invoking the specified method.
User Response:
Refer to the exception in the original error message to determine how to resolve the problem.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Explanation:
A JAXRPC dynamic proxy Stub could not be created for the specified port and service endpoint interface.
User Response:
Check that the specified service endpoint interface is valid.
Explanation:
The service endpoint interface name passed to the getPort method must match a PortType in the WSDL for this Service.
User Response:
Make sure that the service endpoint interface matches a PortType defined in the WSDL.
Explanation:
When calling Service.getPort(Class), the service endpoint interface must specify an Interface.
User Response:
Make sure that the Service Endpoint Interface specifies an interface, not a class.
Last updated:
Library |
Support |
Trademarks |
Feedback