WSWS

WSWS0001E: The path "{0}" is not an absolute path.
WSWS0002E: The parent directory for directory "{0}" does not exist.
WSWS0003E: Protocol must be either "http" or "https", not "{0}".
WSWS0004E: Port must be a positive number, not "{0}".
WSWS0005E: An exception occurred while attempting to extract module "{0}" from the application EAR file into the file system. The exception is "{1}".
WSWS0006E: An exception occured while attempting to construct a WSDLParser on WSDL file "{0}" in module "{1}". The exceptions is "{2}".
WSWS0007E: The Web services Deployment Descriptor ""webservices.xml"" for module {0} has a webservice-description element
whose wsdl-file element is "{1}". The webservice-description element contains a port-component element with the elements
port-qname-namespace = {2} and port-qname-localname = {3}. The WSDL file must contain a targetNameSpace whose value
matches the binding file""s port-qname-namespace, and it must contain a port whose name attribute matches the port-qname-localname.
WSWS0008E: Cannot set the soap address into the published WSDL file. Failed when calling WSLDParser.setSoapAddress()
with wsdlNameSpace={0}, wsdlPortName={1}, and soapAddressURI={2}. The input WSDL file is {3} for module {4}.
WSWS0009E: Caught an exception while saving input WSDL file {0} for module {1} to filename {2}. The exceptions is {3}.
WSWS0010E: Caught an exception while creating a working directory. The exception is {0}.
WSWS0011E: Caught an exception while trying to get an InputStream for file {0} in module {1}. The exception is {2}.
WSWS0012E: Failed while looking in the application ear file""s application.xml for a Web module whose
name is {0}. Perhaps the EndpointEnabler has not been run on the application.
WSWS0013E: The module {0}""s Web services Deployment Descriptor, webservices.xml, has a wsdl-file element
for the file {1}. However, the module""s bindingfile, {2}, doesn""t have a ws-desc-binding element for that WSDL file.
WSWS0015E: Caught an exception while trying to get an InputStream for file {0}. The exception is {1}.
WSWS0016E: The webservices.xml file for module {0} refers to WSDL file "{1}", but the module does not contain a WSDL file by that name.
WSWS0018E: The module {0} does not contain a Web services binding file, {1}. Run the endptEnabler command on the EAR file before installing to add this file.
WSWS0019E: The resource bundle {0} for locale {1} could not be opened. Exception {2}
WSWS0020E: Internal Error: {0}
WSWS0021E: In the Web services Deployment Descriptor for module "{0}", there is no wsdl-file element for webservice-deployment descriptor number {1}.
WSWS0022E: In the Web services Deployment Descriptor for module "{0}", the portcomponent element number {1} of webservice-description element number {2} is not properly formed.
WSWS0023E: The Web services bindings file, {0}, for module {1} does not contain any properly formatted routerModules elements
WSWS0024E: A Web services enabled EJB-JAR module must be deployed to the same server as its router module.
However the EJB-JAR module "{0}" is deployed to "{1}" while its router module. "{2}" is deployed to "{3}".
WSWS0025E: Caught an Exception while copying a file. The source file is {0}. The target file is {1}. The exception is {2}.
WSWS0026E: The file system name "{0}" is needed for a directory in the published WSDL file tree.
However, the name already exists in the file system and is not a directory.
WSWS0027E: In the Web services Deployment Descriptor for module "{0}", there is no webservice-description-name element for webservice-deployment descriptor number {1}.
WSWS0028W: completeTask : Cannot close InputStream "{0}"
WSWS0029E: getServerName: MapModulesToServers :
taskData did not contain a row for moduleURIString "{0}"
WSWS0030E: MapModulesToServersAccessor.getNodeNamesFromServerString:
the string "{0}" does not have the correct syntax.
WSWS0031E: If a servlet is linked to a webservice.xml file""s
port-component, then the module""s web.xml file must contain no more than
one servlet-mapping for that servlet. However, in module {0}, web.xml contains
more than one servlet-mapping element for servlet {1}.
WSWS0032E: If a servlet is linked to from a webservice.xml file""s
port-component, and the module""s web.xml file contains a url-pattern for
that servlet, then the url-pattern must be an exact match pattern, that is
it must not contain an asterisk(""*""). However, in module {0}, web.xml
contains a url-pattern of {1} for servlet {2}.
WSWS0033E: In the webservices.xml file for a Web services enabled
WAR module, a port-component""s service-impl-bean must be servlet-link,
not an EJB-link. However in module {0}, webservice.xml has a port-component
named {1} whose service-impl-bean is not a servlet-link.
WSWS0034E: In module {0}, the WSDL file {1} contains a port named {2},
but there is no corresponding port component in the Web services deployment descriptor.
WSWS0035E: The ibm-webservices-bnd.xml for EJB module {0} says that the
associated router WAR module is {1}. However that WAR module does not exist
in the application.
WSWS0036E: {0} is the router module for Web services enabled
module {1}. The router modules web.xml file must contain a servlet-mapping
stanza with a url-pattern and a servlet-name of {2}, but it does not.
WSWS0037W: The module {0} contains WSDL file {1}. It is recommended
that WSDL files reside in or below WEB-INF/wsdl (for WAR modules)
and META-INF/wsdl (for JAR modules).
WSWS0038E: Error from Web services deploy tool: {0}
WSWS0039W: Warning from Web services deploy tool: {0}
WSWS0040I: Message from Web services deploy tool: {0}
WSWS0041I: Web services deploy task completed successfully.
WSWS0042E: The Web services bindings file for module {0} contains router module stanza whose transport
type is neither jms nor http, but, incorrectly, {1}
WSWS0043E: The EJB module {0} does not have an associated router module
WSWS0044E: Cannot locate the deploy target for module: {0}
WSWS0045E: The router WAR module for EJB module {0} is {1}, but its web.xml is missing a url pattern for port component {2}.
WSWS0046E: The JMS router MDB module {0} does not contain a WebSphere IBM binding file.
WSWS0047E: Cannot find any WSDL files to publish.
WSWS0048I: Web services endpointenabler task completed successfully.
WSWS0049E: The EJB URL suffix {0} is not correctly formatted. It must have the form <property_name>=<value>[&<propety_name>=<value>],
where the valid property_names are {1}. For example {2}
WSWS0050E: The Web services client bind file, ibm-webservicesclient-bnd.xmi, contains port type {0} which is not a valid port type for this client.
WSWS0051W: Custom Property parameter configured for {0} module {1} was ignored.
WSWS0052E: Preferred port mapping could not be created for module {0} client Web service {1}
WSWS0053E: The port {0} is not valid for port type {1} for Web service {2}, module {3}{4}
WSWS0054E: The JMS URL prefix {0} is not correctly formatted.
WSWS0055E: The value for Web service scope, {0}, for a port in module {1} is invalid.
WSWS0056E: The value for Web service client request timeout, {0}, for a port in module {1} is invalid.
WSWS0057E: The value for Web service client overridden endpoint URL, {0}, for a port in module {1} is invalid.
WSWS0058E: The deployed WSDL, {0}, could not be found for the Web service client in module {1}.
WSWS0059E: The Web service client overridden binding namespace, {0}, for module {1} cannot be specified if the overridden endpoint URL is not defined.
WSWS0060W: In module {0}, the WSDL file {1} contains a port named {2},
but there is no corresponding port component in the Web services deployment descriptor.
WSWS0061W: The JMS URL prefix {0} follows the IBM proprietary JMS URL syntax, which has been deprecated.
WSWS1000E: Error: {0}
WSWS1001E: The client process service cannot be accessed.
WSWS1002E: An error occurred while processing the Web services deployment descriptor for module: {0} with error: {1}
WSWS1003E: The WSDL file that is referenced by the client deployment descriptor service reference {0} contains no services.
WSWS1004E: An error occurred while binding client references in java:{0} namespace: {1}
WSWS1005E: The DTD reference in the Web services deployment descriptor is not valid: {0}
WSWS1007E: More than one service is in the WSDL file, but service reference {0} in the client deployment descriptor does not specify which service QName to use.
WSWS1008W: Unable to dump the configuration as part of debug: {0}
WSWS1009W: Warning: [{0}:{1}:{2}] {3}
WSWS1010E: Error: [{0}:{1}:{2}] {3}
WSWS1011E: Error: [{0}:{1}:{2}] {3}
WSWS1012E: Error: Web services is missing the Web container.
WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
WSWS1014W: Java class {0} that is specified in provider {1} cannot be loaded. The provider is skipped. The exception is {2}.
WSWS1015W: Servlet for servlet-link {0} not found. The port-component {1} is skipped.
WSWS1016E: Multiple ""port-component-name"" elements with the value {0} were found.
WSWS1017E: The JSR 109 JAX-RPC mapping file {0}, as specified in the client deployment descriptor for service reference {1} cannot be read.
WSWS1018W: For handlers {0} the handler {1} was not added due to a role statement {2} that is not valid.
WSWS1019W: For handlers {0} the handler {1} is not added because of a flow statement {2} that is not valid.
WSWS1020E: Unable to parse file {0}
WSWS1021W: Warning: No services to deploy.
WSWS1022W: Client reference {0} not of expected type {1} in java:comp namespace.
WSWS1023W: The client reference was not found in java:comp namespace.
WSWS1025E: Error: Resource {0} was not found.
WSWS1026E: Error: Resource {0} was not loaded: {1}
WSWS1027W: Warning: Web services MBean could not be registered: {0}
WSWS1028E: Error: Unable to initialize EJBCollaborator: {0}
WSWS1029E: Error: {0}: Metadata service lookup failed: {1}
WSWS1030E: An error occurred while binding service references: {0}
WSWS1031E: {0}: An error occurred while binding service references in the java:{1} namespace.
WSWS1032E: {0}: An error occurred while binding service reference {1} in the java:{2} namespace.
WSWS1033W: Java class {0} that is specified for handler {1} cannot be loaded. The handler is skipped. The exception is {2}.
WSWS1034W: No port component binding with the name {0} was found in bindings file {1}.
WSWS1035E: An error occurred in {0}: context information: {1}
WSWS1037E: The JSR 109 JAX-RPC mapping file {0}, as specified in <webservice-description> {1} in deployment descriptor {2} for module {3} was not found in application {4}. This Web service description is ignored.
WSWS1038W: No setter method on {0} with a method name {1} was found for reference {2}. The service name cannot be changed to {3}.
WSWS1039E: The Web services binding file {0} was not found in module {1} in application {2}. This file is required for this type of module.
WSWS1040W: The Web services binding file {0} was not found in module {1} in application {2}. Certain functionality, such as Web services security is not available.
WSWS1041W: No Web service description binding is found in the Web services binding file {0} with the name {1}.
WSWS1042E: An error occurred in loading the configuration for {0}. The exception is {1}.
WSWS1043E: An error occurred in the configuration. More than one security binding is defined, but the program cannot determine which one to use without the WSDL service port.
WSWS1044E: An error occurred in the configuration. More than one security deployment descriptor is defined, but the program cannot determine which one to use without the WSDL service port.
WSWS1045E: An error occurred in loading {0} configuration for {1}. The service cannot be started.
WSWS1046E: The ibm-webservices-bnd.xmi file for enterprise bean module {0} says that the
associated router module is {1}. However, that router module does not exist in the application.
WSWS1047W: The ibm-webservicesclient-bnd.xmi defaultMappings information for serviceRefLink {0} does not correspond
to the information in the WSDL file. One or more of the following values are incorrectly specified in the ibm-webservicesclient-bnd.xmi file:
portTypeLocalName {1}, portTypeNamespace {2}, portLocalName {3}, or portNamespace {4}.
WSWS1048E: J2EE 1.3 {0} contains unexpected component-scoped service references with no component specified.
WSWS1049E: J2EE 1.3 {0} is missing component-scoped service references.
WSWS1050W: J2EE 1.3 {0} component-scoped service references do not match the enterprise beans.
WSWS1051W: The Web service-enabled enterprise bean does not have any defined Web service router modules.
WSWS1052E: The service endpoint is not defined. Application ""{0}"", Module ""{1}"", enterprise bean ""{2}"".
WSWS1053E: The service endpoint of the ejb-jar.xml ({0}) and webservices.xml ({1}) files do not match. Application ""{2}"", Module ""{3}"", enterprise bean ""{4}"".
WSWS1054E: Internal Error: An EJB object is expected at dispatcher invoke.
WSWS1055E: Internal Error: An EJB object is expected at dispatcher cleanup.
WSWS1056E: Internal Error: The method ""{0}"" on class ""{1}""was not found.
WSWS1057E: Internal Error: The Web services global configuration was not loaded.
WSWS1058E: Application {0}, module {1}, file {2}, port-component-name {3}: service-impl-bean ejb-link {4} does not correspond to any enterprise bean name in the ejb-jar.xml file.
WSWS1059E: No WSDL services exist with qname {0}.
WSWS1060E: Received request {0} for unregistered system service endpoint {1}.
WSWS1061E: No system endpoint router is defined for request {0}.
WSWS1062I: The SOAP Container service has been initialized.
WSWS1063E: No Web services system service is available.
WSWS1064E: A transport header key of null or length of zero is specified. This header key is not valid and will be ignored.
WSWS1065E: A transport header value of null or length of zero is specified for header key {0}. This header key is not valid and will be ignored.
WSWS1066W: {0} in {1} does not contain a componentScopedRefs element, which is required for configuring security.
WSWS1067E: The loading of the metadata for JAX-RPC module {0} has failed. The exception is: {1}
WSWS1068E: Internal error. A response from a web service endpoint in an Enterprise Java Beans module could not be processed because an endpoint manager
could not be located.
WSWS2000I: {0}
WSWS2001I: The trace data is displayed on the standard output stream.
WSWS2002I: Enter the name of an existing file.
WSWS2003I: Backing up the enterprise archive (EAR) file to: {0}~
WSWS2004I: IBM WebSphere Application Server Version 8.5.5
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
WSWS2006I: Enter the name of your enterprise archive (EAR) file: \
WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2010.
WSWS2008E: Missing value for the -transport parameter.
WSWS2009E: Missing value for the -properties parameter.
WSWS2010I: Read properties from file: {0}
WSWS2011E: An unrecognized command-line parameter was found: {0}
WSWS2012I: The endpoint enabler is using the following properties:
WSWS2013E: An unrecognized transport was specified: {0}
WSWS2014E: "EAR filename" parameter is missing or empty.
WSWS2015E: The props parameter is missing.
WSWS2016I: Loading enterprise archive (EAR) file: {0}
WSWS2017I: Found enterprise bean module: {0}
WSWS2018I: Finished processing enterprise archive (EAR) file {0}.
WSWS2019I: Enabling enterprise bean module {0}...
WSWS2020I: Finished enabling enterprise bean module {0}...
WSWS2021I: Skipping the enterprise bean module {0} because it contains no Web services.
WSWS2022I: Skipping {0} router module for enterprise bean module {1} because it already contains a router for this transport.
WSWS2023I: Skipping {0} router for enterprise bean module {1} due to the skip property.
WSWS2024I: Adding {0} router for enterprise bean 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 enterprise bean module {1} [{2}]:
WSWS2030I: Enter {0} context root for enterprise bean module {1} [{2}]:
WSWS2031I: Enter {0} listener input port name for enterprise bean module {1} [{2}]:
WSWS2032E: The destination type that is specified: {0} is not valid.
WSWS2033I: Enter {0} destination type for enterprise bean module {1} [{2}]:
WSWS2034I: Usage syntax: endptEnabler [options] [trace options] [<ear-file-name>]


<ear-file-name> represents the name of the enterprise archive (EAR) file to process.

If not specified, the user is prompted for this value.


Options:

-help, -h, -?

   Print this message and exit.

-verbose, -v

   Print detailed progress messages while the EAR file is

   being processed.

-quiet, -q

   Do not print progress messages while the EAR file is

   being processed.

-properties <properties-file-name>

-p <properties-file-name>

   Load and use the properties that are contained in

   <properties-file-name>.

-transport <transports-list>

-t <transports-list>

   The comma-separated default list of transports for

   which router modules to create.

   The currently-supported transports include http and jms.

-classpath <classpath>

-cp <classpath>

   Set additional directories, zip, and jar files in search path.

   Separate multiple entries with the file separator character

   specific to your operating system.

-endpointType <endpoint type>

-e <endpoint type>

   Specify the endpoint type.

   The currently-supported endpoint types include jaxws, jaxrs and all(both jaxws and jaxrs)

-enableHttpRouterSecurity

   Each HTTP router module that is created by endptEnabler are protected if the enterprise beans

   in the corresponding enterprise bean module are also protected.

   Note that if this option is not specified, no security information

   is added to the HTTP router module, even if the corresponding enterprise bean module

   contains security information.


{0}


Examples:

   endptEnabler

   endptEnabler myearfile.ear

   endptEnabler -v myearfile.ear

   endptEnabler -v -transports jms myearfile.ear

   endptEnabler -q -p myenabler.props -t http myearfile.ear

   endptEnabler -e jaxrs myearfile.ear
WSWS2035E: An error occurred loading the JSR 109 deployment descriptor {0} for enterprise bean module {1}.
WSWS2036I: Saving the enterprise archive (EAR) file {0}...
WSWS2037I: Finished saving the enterprise archive (EAR) file.
WSWS2038I: Trace is enabled for the following components: {0}
WSWS2039I: Trace data will be logged in file: {0}
WSWS2040W: The enterprise bean module {0} contains protected enterprise beans,

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 enterprise bean module {0} contains at least one unprotected enterprise bean 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} is already configured for JMS router module {1}.
WSWS2043I: Activation spec JNDI name: {0}
WSWS2044I: Enter {0} activation spec JNDI name for enterprise bean module {1} [{2}]:
WSWS2045I: EndpointEnabler failed with error:
{0}
WSWS2046W: The {0} WAR module generated by EndpointEnabler contains multiple servlets with
the same URL pattern. This must be fixed before installing the application.
WSWS2047I: URL pattern for port {0}: {1}
WSWS2048I: Missing value for the -classpath parameter.
WSWS3000I: WSDL2Java emitter

Usage: WSDL2Java [options] WSDL-URI

Important Options:

   -r, -role <argument>

      the J2EE role that identifies which files to generate. Valid arguments are:

         "develop-client" : (default) generates files for client development

         "develop-server" : generates files for server development

         "deploy-client" : generates binding files for client deployment

         "deploy-server" : generates binding files for server deployment

         "client" : combination of "develop-client" and "deploy-client"

         "server" : combination of "develop-server" and "deploy-server"

   -c, -container <argument>

      indicates the J2EE container. Valid arguments are:

         "none" : indicates no container

         "client" : indicates client container

         "ejb" : indicates EJB container

         "web" : indicates Web container

      If client role the default argument is "none".

      If server role the container must be either "ejb" or "web".

      The same container option must be used for both development and deployment.

   -o, -output <argument>

      output directory for emitted files.

   -m, -inputMappingFile <mapping-file>

      the location of the Java to WSDL mapping.

   -i, -introspect

      introspect existing classes to determine mapping details.

   -C, -classpath <paths>

      classpath to use for class introspection.

Other Options:

   -h, -help

      print this message and exit.

   -X, -helpX

      print extended options.

   -v, -verbose

      print verbose informational messages.

   -N, -NStoPkg <namespace>=<package>

      mapping of namespace to package.

      Alternatively declare this information in the mapping file.

   -O, -timeout <argument>

      number of seconds to wait for accessing WSDL-URI.

      (default is 45 seconds), specify -timeout -1 to disable.

   -R, -retry <argument>

      how many times to re-attempt to load a WSDL-URI, or one of

      it"s imported documents after initial attempt times out.

   -g, -genResolver

      generate an absolute-import resolver.

   -u, -useResolver

      specify an absolute-import resolver to use during parsing.

   -d, -deployScope <argument>

      Valid arguments are: "Request", "Session", "Application".

      Adds a "scope" attribute to the ibm-webservices-bnd.xmi file

      when it is created to specify how often to create a new bean.

      Only applicable when role is "develop-server" or "server".
WSWS3001I: Info:

Extended Options:

   -U, -user <argument>

      login user name to access the WSDL-URI.

   -P, -password <argument>

      login password to access the WSDL-URI.

   -a, -all

      generate java files for all types, even unreferenced ones.

   -z, -noDataBinding

      map all types (including base schema types) to SOAPElement.

   -t, -testCase

      emit template junit testcase class for testing Web service.

   -D, -Debug

      print debug information.

   -f, -fileNStoPkg <argument>

      file of NStoPkg mappings (default NStoPkg.properties).

   -j, -genJava <argument>

      generate Java files. Valid arguments are:

         "No"

         "IfNotExists" (default)

         "Overwrite"

   -s, -javaSearch <argument>

      when -genJava is set to "IfNotExists",

      determines how file existence is detected.

      Valid arguments are:

         "File" (default)

         "Classpath"

         "Both"

   -x, -genXML <argument>

      generate XML and XMI files. Valid arguments are:

         "No"

         "IfNotExists" (default)

         "Overwrite"

   -E, -genEquals <boolean>

      Enable the hashcode/equal generation. Valid arguments are:

         "yes"

         "no" (default)

   -I, -genImplSer <boolean>

      Have generated beans implement java.io.Serializable. Valid arguments are:

         "yes"

         "no" (default)

   -T, -properties <option> | <option>=<value>

      specify extended option(s) and any values it may require.

      example: -properties key1=value1;key2;key3=value3

      example: -properties key1=value1 -properties key2

      Alternatively declare this information in a properties file.

   -b, -propertiesFile <argument>

      filename of a properties file that contains a list of extended properties

      Example of file content:

         key1=value1

   -y, -noWrappedArrays

      Disable .NET wrapped array pattern. Generate beans containing arrays.

   -w, -noWrappedOperations

      Disable .NET wrapped operation pattern. Generate request and response beans.
WSWS3002I: Java2WSDL emitter

Usage: Java2WSDL [options] class-of-portType

Options:

   -location <argument>

      web service location url

   -output <wsdl>

      output WSDL file name

   -input <argument>

      input wsdl file name

      used to build wsdl from existing wsdl information

   -bindingTypes <argument>

      list of binding types to include in the wsdl file

      the default is "http"

      examples:

       -bindingTypes http,ejb

       -bindingTypes http,jms

   -style <argument>

      valid arguments:

         document (the default): generate document style wsdl

         rpc: generate rpc style wsdl

   -use <argument>

      valid arguments:

         literal (the default): literal use

         encoded: encoded use

   -transport <argument>

      This option has been deprecated.

      Use the -bindingTypes option instead.

   -portTypeName <portType>

      name of the portType

      defaults to name of the input class

   -bindingName <binding>

      name of the binding

      defaulted from portType if not specified

   -serviceElementName <service>

      name of the service

      defaulted from portType name if not specified

   -servicePortName <port>

      name of the port

      defaulted from -location if not specified

   -namespace <argument>

      target namespace of WSDL

   -PkgtoNS <package>=<namespace>

      mapping of package names to namespaces

   -implClass <class-name>

      class that contains implementation of methods in

      class-of-portType. The debug information in the class is used

      to obtain the method parameter names, which are used to set

      the WSDL part names.

   -extraClasses <classes>

      other classes that should be added to the WSDL

   -classpath <paths>

      classpath to use for class introspection.

   -verbose

      display verbose messages

   -elementFormDefault <qualified | unqualified>

      indicate elementFormDefault usage

   -attributeFormDefault <qualified | unqualified>

      indicate attributeFormDefault usage

   -help

      displays this message

   -helpX

      displays extended options
WSWS3003I: Info:

Extended Options:

   -wrapped <boolean>

      indicate if WSDL should respect "wrapped" rules

      valid only for -style document and -use literal.

      the default is true.

   -stopClasses <argument>

      space or comma separated list of class names which will stop

      inheritance search when processing classes

   -methods <argument>

      space or comma separated list of method names from the SEI which

      are to be exposed in the output WSDL

   -soapAction <argument>

      valid arguments:

         OPERATION sets soapAction field to the operation name.

         NONE sets soapAction field to "".

   -outputImpl <file>

      specify if you want both interface and implementation WSDLs

   -locationImport <argument>

      location of interface WSDL file

   -namespaceImpl <argument>

      target namespace for implementation WSDL

   -MIMEStyle <argument>

      valid arguments:

         AXIS: AXIS style MIME representation

         WSDL11 (default): WSDL 1.1 MIME representation

         swaRef: WS-I BP 1.1 representation (swaRef where appropriate)

   -propertiesFile <argument>

      filename of a properties file that contains a list of class names

      which should be added to the type section of the output WSDL.

      Example of file content:

         extraClasses=com.ibm.Class1,com.sun.Class2,org.apache.Class3

   -voidReturn <argument>

      valid arguments:

         ONEWAY:treat methods with void returns as one-way

         TWOWAY:treat methods with void returns as two-way

   -debug

      display debug messages

   -properties <property settings>

      sets binding-specific properties to be used by binding generators

      example: -properties prop1=value1,prop2=value2



Supported binding-specific properties:
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}.

Child element {1} does not belong in namespace {2}.

Most likely, a third party web services platform has sent an incorrect SOAP message.
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 <port binding=".."> is fully qualified.
WSWS3104E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document {1}.
Hint: make sure <port binding=".."> is fully qualified.
WSWS3105E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document.
Hint: make sure <binding type=".."> is fully qualified.
WSWS3106E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document {1}.
Hint: make sure <binding type=".."> is fully qualified.
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".
WSWS3119W: Warning: 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.
WSWS3124W: Warning: Invalid -genJava option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
WSWS3125W: Warning: 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 <body> tag.
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 administrator 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 attempting to load:
{0}.
Make sure the specified URL is accessible.
If it is, try increasing ""timeout"" and/or ""retry"" default settings in the WSDL2Java emitter.
WSWS3246E: Error: SOAPFault.addDetail called when a detail is present.
WSWS3247E: Error: No target endpoint address has been set on the Stub or Call object.
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: Could not resolve to an operation. The message contains an element
named ""{0}"", but this does not match any operation of the target port. Debug: {1}
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 NONE or OPERATION.
WSWS3281E: Error: Tried to invoke method ""{0}"" with argument classes ""{1}"" against object ""{2}"" of class ""{3}"". 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 <class-of-portType> has already been specified as, {0}. It cannot be specified again as {1}.
WSWS3287E: Error: The <class-of-portType> was not specified.
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 parameter names in bytecode: unexpected end of file.
WSWS3327E: Error: Error looking for parameter 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 synchronized 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 <soap:fault> element inFault "{0}" in operation "{1}", in binding {2}
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, Version 1.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 cannot 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.
WSWS3419E: The current node is not a Text node, and it either has more than one child node or has a child node that is not a Text node.
WSWS3420E: Error: Emitter failure. Part {0} of operation {1} must be a type part.
WSWS3421E: Error: The service interface ""{0}"" does not subclass ""javax.xml.rpc.Service"".
WSWS3422E: Error: Cannot instantiate {0}.
WSWS3423E: Error: "javax.xml.soap.write-xml-declaration" property has to be either true or false.
WSWS3424E: Error: List value of type {1}, is not a simple type.
WSWS3425I: From target realm: {0}.
WSWS3426I: HTTP Basic Authentication information has been received.
WSWS3427I: No HTTP Basic Authentication Information has been received.
WSWS3428W: Warning: Found an old J2EE 1.3 version of the DD. A new J2EE DD version will be written.
WSWS3429W: Warning: Found old J2EE 1.3 {0} file. This indicates a version mismatch - a new J2EE DD version will be written.
WSWS3430E: Invalid CharacterEncoding: {0}.
WSWS3431E: Error: No Service Endpoint Class found for port {0}.
WSWS3432E: Error: Exception thrown while invoking method ""{0}"" against object ""{2}"" of class ""{3}"".
WSWS3433E: Internal Error: No Processor assigned to port {0}.
WSWS3434E: Unable to load configuration file
WSWS3435E: Error: Invalid date/time. Received an empty string for a date/time value.
WSWS3436E: Error: Invalid time: Received an empty string for a time value.
WSWS3437E: Error: Invalid date: Received an empty string for a date value.
WSWS3438E: Error: The service locator ""{1}"" does not subclass the service interface ""{0}"".
WSWS3439E: Error: The contents of the SOAP body are encrypted. The target operation cannot be invoked. The body contains an element with the name: {0}.
WSWS3440W: Warning: The WSDL2Java emitter does not understand qname {0} specified in field {1} of construct {2} in the mapping file: {3}. The information in the mapping file corresponding to this qname will be ignored.
WSWS3441W: Warning: The WSDL2Java emitter cannot find the corresponding java-xml-type-mapping construct for the exception-mapping with wsdl-message ({0}) and exception-type ({1}) in file {2}.
WSWS3442E: Error: No output for Call.{0}.
WSWS3443E: Handler {0}: Protected state violation: SOAPPart missing/removed.
WSWS3444E: Handler {0}: Protected state violation: SOAPMessage missing/removed.
WSWS3445E: Handler {0}: Protected state violation: Unexpected exception. Review error log for details.
WSWS3446E: The endpoint address URL is missing.
WSWS3447E: Error: Could not get a secure socket factory with the SSL settings of JSSE.
WSWS3448I: Info: HTTP Proxy Host name: {0}, Proxy Port: {1}, Proxy User name: {2}, Proxy Password: {3}
WSWS3449I: Info: HTTPS Proxy Host name: {0}, Proxy Port: {1}, Proxy User name: {2}, Proxy Password: {3}
WSWS3450I: Info: SSL configuration is from {0}.
WSWS3451I: Info: Response from Proxy for HTTP CONNECT: {0}.
WSWS3452E: Internal Error: Attempted to generate code without first parsing WSDL file.
WSWS3453I: File {0} will NOT be written. Write permission denied by underlying file system.
WSWS3454E: 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}
WSWS3455I: Error: Invalid -javaSearch option argument "{0}". Valid options are "File", "Classpath", or "Both". Defaulting to "File".
WSWS3456E: Error: The onStartChild method of {0} does not know understand how to process element {1}. Processing cannot continue.
WSWS3457W: Warning: The WSDL2Java emitter has found relative namespace {0} in the WSDL, and cannot transform it to an absolute namespace.
WSWS3458E: ---------- WSDL2Java VALIDATION ERROR ----------

Incompatible return types found at SEI method: "{0}"

   Existing Java return type = {1}

   WSDL defined return type = {2}
WSWS3459E: ---------- WSDL2Java VALIDATION ERROR ----------

Incompatible parameter types found at SEI method: "{0}"

   Existing Java parameter type = {1}

   WSDL defined parameter type = {2}
WSWS3460E: ---------- WSDL2Java VALIDATION ERROR ----------

Incompatible field types found in Java class: "{0}"

   Existing Java class field type = {1}

   WSDL defined field type = {2}
WSWS3461E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Enumeration class is invalid: "{0}"

   Missing the following JAX-RPC required method = {1}
WSWS3462E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Enumeration class is invalid: "{0}"

   Contains invalid method = {1}
WSWS3463E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Bean class is invalid: "{0}"

   Does NOT contain a public default constructor = {1}
WSWS3464E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Bean class is invalid: "{0}"

   It extends a non-bean class = {1}
WSWS3465E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Bean class is invalid: "{0}"

   It does not define a bean property for the following data member = {1}
WSWS3466E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Fault class is invalid: "{0}"

   It does not extend = {1}
WSWS3467E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Fault class is invalid: "{0}"

   Does not implement a valid public constructor: "{1}", containing {2} parameters.
WSWS3468E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Fault class is invalid: "{0}"

   It does not define a property for the following data member = {1}
WSWS3469E: ---------- WSDL2Java VALIDATION ERROR ----------

Incompatible parameter types found at Fault class method: "{0}"

   Existing Java parameter type = {1}

   WSDL defined parameter type = {2}
WSWS3470E: Error while running class ""{0}"".
WSWS3471W: Binding {0} has already been generated and will not be
re-generated.
WSWS3472W: 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.
WSWS3473E: No binding generator was found for binding type ""{0}"".
WSWS3474I: Found a binding generator for binding type ""{0}"".
WSWS3475W: A binding specific location property was not specified
for the requested {0} binding. The default location ""{1}"" will be used.
WSWS3476W: The generic -location option should not be used when
more than one binding type has been requested.
WSWS3477I: Binding-specific properties are {0}
WSWS3479E: The ""{0}"" property is required, but was not specified.
WSWS3480E: One or more errors occurred while validating the input properties.
WSWS3481E: There is no binding defined for {0} RequestSender.
WSWS3482E: There is no deployment descriptor defined for {0} RequestSender.
WSWS3483E: Could not find WSDL file ""{0}"" within the EAR.
WSWS3484E: Caught {0} while trying to read WSDL file ""{1}"": {2}
WSWS3485E: No WSDL services were found for namespace ""{0}"".
WSWS3486E: The ClassLoader parameter was passed in as null.
WSWS3487E: The port name and service ref name are both null.
WSWS3488E: Error: This SOAPElement is not a swaRef - it is not a reference to an attachment.
WSWS3489E: Error: Mime type {0} does not match object type {1}.
WSWS3490E: Error: The system cannot load the file referenced within {0}. The problem is with {1}.
WSWS3491E: Error: Reading import file: {0}
WSWS3492W: Warning: Invalid option combination: style={0} and use={1}

       Will default to document/literal.
WSWS3493E: Error: Invalid combination: style="{0}" and use="{1}"

For binding="{2}" and binding operation="{3}"
WSWS3494I: syncTimeout value is {0} seconds to wait for response to the
current SOAP over {1} request.
WSWS3495I: {0} is used as the final endpoint address.
WSWS3496I: {0} is used as the proxy address.
WSWS3497I: Status in the HTTP response: {0}, {1}
WSWS3498E: No HTTP status has been received for the current HTTP response.
WSWS3499W: Redirected new location: {0}
WSWS3500I: Required service: {0} from JNDI namespace: {1}
WSWS3501E: Failures from the Channel Framework service: {0}
WSWS3502E: Unsupported schema for HTTP: {0}
WSWS3503I: Updated configuration of the outbound connection for key: {0}
WSWS3504E: Failed to retrieve HTTP(S) proxy information for the proxy connection.
WSWS3505I: Creating channel named: {0}
WSWS3506I: Found channel named: {0}
WSWS3507I: Creating channel chain named: {0}
WSWS3508I: Found channel chain named: {0}
WSWS3509I: Expect 100 Continue in the HTTP response...sending HTTP
request headers only to connection: {0}
WSWS3510I: Sending both HTTP request headers and body message to
connection: {0}
WSWS3511I: Sending current request to {0} in version: {1}
WSWS3512E: Unsupported HTTP version: {0}
WSWS3513E: Invalid HTTP response received from the connection for: {0}
WSWS3514E: No HTTP response body is available from the connection for: {0}
WSWS3515E: Failures with the SSL Channel services: {0}
WSWS3516I: Received cookie for HTTP header: {0} in the response from
connection to: {1}
WSWS3517I: Target address to connect: {0}
WSWS3518I: Target address: {0} is already connected.
WSWS3519I: Disconnecting target address: {0}. Mark the object
to be closed: {1}
WSWS3520I: Target address: {0} is already disconnected.
The connection object: {1} is already marked.
WSWS3521I: Reset the connection object for target address:
{0}. Connection is persistent? {1}
WSWS3522I: Read keystore password property for: {0}
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}
WSWS3524E: 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.
WSWS3525E: Exception occurred while loading "META-INF/services/CustomBindingProvider.xml" files.
WSWS3526W: No namespace was found for a mapping defined in the file {0}.
WSWS3527I: Discovered and loaded the custom binding provider from the file: {0}
WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ----------

   Extension base mismatch between existing Bean and WSDL document.

   Existing Bean class: "{0}"

   Extends the following class: {1}

   However the following extension base

   is specified in the WSDL document: {2}
WSWS3529I: Outbound connection object expired: {0}. Time from the
last access to the object: {1} millieseconds.
WSWS3530I: Found an existed outbound connection object: {0} in the
cache.
WSWS3531I: Created a new outbound connection object: {0} in the
cache using virtual connection factory: {1}
WSWS3532I: Returning a closed outbound connection object: {0} to
the cache.
WSWS3533I: Returning an outbound connection object: {0} to
the cache.
WSWS3534W: Encountered unknown outbound connection object: {0}
WSWS3535I: Remove outbound connection object: {0} from the cache.
WSWS3536I: New connection established with virtual connection
object: {0}
WSWS3537I: Connection established already with virtual connection
object: {0}
WSWS3538W: A connection is attempted with outbound connection
object that is already marked to be closed: {0}
WSWS3539E: Exception {0} is caught. Release related virtual
connection object:{1} and outbound service context: {2}
WSWS3540I: Key {0} found for connection table lookup: {1}
WSWS3541E: Error: Attribute {0} is referenced but not defined.
WSWS3542I: Each failed HTTP connection will be retried until succeeds.
WSWS3543I: Number of retries for failed HTTP connection: {0}.
WSWS3544W: Exception caught: {0}. HTTP connection
to retry: {1}.
WSWS3545I: Released object: {0}
WSWS3546I: Current size of the connection object pool: {0}
WSWS3547I: Outbound connection group is created for key: {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}.
WSWS3550E: Error: The MessageContext specifies Style {0} but the OperationDesc specifies Style {1}.
WSWS3551E: Error: The MessageContext specifies Use {0} but the OperationDesc specifies Use {1}.
WSWS3552E: Error: Cannot load the Java class for the custom binder: {0}.
WSWS3553E: Error: The value of -MIMEstyle must be AXIS, swaRef or WSDL11.
WSWS3554E: Error: Group {0} is referenced but not defined.
WSWS3555E: Error: AttributeGroup {0} is referenced but not defined.
WSWS3556I: No compression will be performed for HTTP Content-Encoding.
WSWS3557I: Compression type of <gzip(x-gzip)> enabled? {0}
WSWS3558I: Compression type of <deflate> enabled? {0}
WSWS3559I: Using {0} type of HTTP Channel.
WSWS3560W: Unable to get an Inprocess Channel: {0}. Proceed now with
a network type of Channel.
WSWS3561E: Mapped to cluster name <{0}> using - host: {1}, port: {2}, URI
path: {3}
WSWS3562W: Warning: The -wrapped option setting is only useful if -style DOCUMENT and -use LITERAL. Processing continues and the wrapped setting is ignored.
WSWS3563I: Accept-Encoding header from incoming HTTP request = {0}
WSWS3564I: ChannelFramework EndPoint object: {0} is mapped, using
Identity object of {1}
WSWS3565E: Error: Invalid endpoint argument to Service.getPort {0}
WSWS3566E: Error: Invalid port for Service.createCall: {0}
WSWS3567E: Error: Invalid operation for Service.createCall: {0}
WSWS3568E: ---------- WSDL2Java VALIDATION ERROR ----------

   Existing Bean class is invalid: "{0}"

   It does not define a set method for the following data member = {1}

   A get method was found = {2}
WSWS3569I: Inbound {0} {1} request:

Content-Type: {2}

Message contents:
WSWS3570I: Inbound {0} {1} response:

Content-Type: {2}

Message contents:
WSWS3571I: Outbound {0} {1} request:

Content-Type: {2}

Message contents:
WSWS3572I: Outbound {0} {1} response:

Content-Type: {2}

Message contents:
WSWS3573E: Cluster identity object: {0} found by the RequestMapper
using original endpoint address: {1}. If the identity object is null, transport will proceed to use
default channels for connections.
WSWS3574E: ---------- FATAL ERRORS ENCOUNTERED ----------

   GENERATION OF ARTIFACTS HAS BEEN SUSPENDED.

   See messages to follow for more details.
WSWS3575E: Failed to set the protection for the SOAPBody.
WSWS3576I: Info: Changed java name {0} to {1} for xml construct {2} due to mapping file reference.
WSWS3577I: Info: Changed java name {0} to {1} for xml construct {2} due to custom binding designation.
WSWS3578I: Info: Changed java name {0} to {1} for xml construct {2} due to java reflection.
WSWS3579I: Info: Introspecting SEI {0}. JavaClass is: {1}
WSWS3580I: Info: Introspecting class for xml construct {0}. JavaClass is: {1}
WSWS3581E: Error: PortType operation has no corresponding binding operation: name = {0}, input name = {1}, output name = {2}
WSWS3582E: The ""{0}"" property is invalid unless -bindingTypes http (or no bindingTypes) is also specified.
WSWS3583E: The ""{0}"" property is invalid unless -bindingTypes jms is also specified.
WSWS3584E: The ""{0}"" property is invalid unless -bindingTypes ejb is also specified.
WSWS3585W: Warning: PortType operation has no corresponding binding operation containing the same number of input and output parameter names; name = {0}, input name = {1}, output name = {2}
WSWS3586I: Invoking method: {0}() of class: {1}
WSWS3587I: Received Cluster Identity object: {0} from WS-Addressing.
If the Identity object is null, transport attempts to map one by the RequestMapper.
WSWS3588I: Could not map an Cluster Identity object: {0}
to a valid endpoint. Transport attempts to use default channels for connections.
WSWS3589I: Exception caught: {0} resolving the endpoint.
Proceed to next option using RequestMapper.
WSWS3590I: Exception caught: {0} resolving the endpoint.
Proceed to next option using default channels.
WSWS3591I: An exception which was defined in the WSDL for the the operation has been thrown by the service endpoint. This may not indicate an error.
WSWS3592E: Error: Could not resolve to an operation. The message contains body elements
named ""{0}"", and this matches multiple operations ""{1}"". Debug: {2}
WSWS3593E: Error: Operations {0} and {1} have the same parameters elements in their input
request message. Please change the WSDL.
WSWS3594E: Error: Methods {0} and {1} have the same parameters names. A document literal non-wrapped wsdl cannot be produced.
WSWS3595I: Current pool size: {0}. Connections-in-use size: {1}. Configured pool size: {2}
WSWS3596I: Current thread: {0} is going to wait for notification.
WSWS3597I: Current thread: {0} is going to wait {1} milliseconds for notification.
WSWS3598I: Notify the next waiting thread.
WSWS3599I: The current thread: {0} has been notified.
WSWS3600I: The connection wait timed out.
WSWS3601E: An unexpected integrity problem occurred with the connection pool.
WSWS3602I: Current endpoint: {0}. New endpoint: {1}
WSWS3603E: Error: IllegalArgumentException: null parameter passed to the addTextNode method
WSWS3700E: Error: Non-whitespace character content ({0}) was detected in the {1}.
Processing cannot continue.
WSWS3701E: Error: An exception was encountered.
Use the wsdeploy command to deploy your application.
The exception is {0} {1}
WSWS3702E: Error: Could not resolve to an operation. The message contains an element
named ""{0}"", but this element does not match any operation of the target port.

However, the following operation(s) ({1}) have similar information but are a different style.

This difference might indicate that the client sent a {2} message and the server is expecting a {3} message.

Debug: {4}
WSWS3703E: Error: The WSDL operation, {2}, contains multiple {1} parameters that
are mapped to the same qname: {0}.
WSWS3704W: Warning: Java2WSDL encountered a inner nested class named {0} in the input.
Inner classes are not supported. Generation will continue.
WSWS3705E: ERROR: Document: {0}, imported by a wsdl:import from within: {1},

is neither a schema or a WSDL file.
WSWS3706W: WARNING: NOT WS-I Compliant.

   Document: {1} is using a wsdl:import to import a schema document: {0}

   WS-I requires wsdl:imports to import only WSDL documents.
WSWS3707W: WARNING: NOT WS-I Compliant.

   The wsdl:import namespace attribute= {0}

   in document= {1}, is a relative URI.

   WS-I requires wsdl:import namespaces to be absolute.
WSWS3708W: WARNING: NOT WS-I Compliant.

   The schemaLocation attribute of the xsd:import: {0}

   does NOT resolve to a document whose root element is a schema.
WSWS3709E: Internal Error: Unsupported content found in web services engine.
Content of type {0} was found.
WSWS3710E: Internal Error: Attempt to change encoding on WebServicesInputSource from
{0} to {1}.
WSWS3711E: Internal Error: WebServicesInputSource internal state error: {0}
WSWS3712E: Internal Error: Attempt to write empty WebServicesInputSource.
WSWS3713E: Connection to the remote host {0} failed.
Received the following error: {1}
WSWS3714W: WARNING: NOT WS-I Compliant.

   WS-I specifies that XML Schema "{2}" statements only appear in

   the xsd:schema element of the types section.

   Document: {0}, is using a non-compliant Schema "{2}" to {2}: {1}
WSWS3715E: FATAL ERROR:

   The WSDL document: {0}

   contains a wsdl:import for namespace= {1},

   but does not specify a "location" attribute.

   Add a "location" attribute to the specified wsdl:import element.
WSWS3716W: WARNING: NOT WS-I Compliant.

   The WSDL document: "{0}"

   defines a "wsdl:import" element AFTER defining the following element: "{1}"

   WS-I specifies that "wsdl:import" elements MUST precede all other elements

   from the WSDL namespace except for "wsdl:documentation".
WSWS3717W: WARNING: NOT WS-I Compliant.

   The WSDL document: "{0}"

   defines a "wsdl:types" element AFTER defining the following element: "{1}"

   WS-I specifies that "wsdl:types" elements MUST precede all other elements

   from the WSDL namespace except for "wsdl:documentation" and "wsdl:import".
WSWS3718W: WARNING: Null namespace and targetNamespace NOT supported.

   Document: {0}

   does not define a ""namespace"" attribute when importing: {1}.

   The file being imported does not define a ""targetNamespace"" either.

   Please make sure, both, the ""namespace"" attribute and the ""targetNamespace""

   of the imported file, are defined and equal in value.
WSWS3719W: WARNING: NOT WS-I Compliant.

   Document: {0}

   imports: {1},

   with namespace attribute value of: {2}

   However, {1},

   contains a targetNamespace value of: {3}

   WS-I requires the import namespace attribute and the targetNamespace

   of the imported document to be equal.
WSWS3720I: Dynamic Work Load Management Client is enabled: {0}
WSWS3721I: Info: {0} is an asynchronous operation indicated by WS-Addressing.
WSWS3722I: Info: {0} is a Request-Response operation.
WSWS3723E: Error: The value stored as the "{0}" property must be of type ""java.util.HashMap"",
but was found to be of type "{1}".
WSWS3724E: Error: The java.util.HashMap stored as the "{0}" property was empty.
WSWS3725E: Error: The java.util.HashMap stored as the "{0}" property contains a null key.
WSWS3726E: Error: The java.util.HashMap stored as the "{0}" property should contain keys of type
"javax.xml.namespace.QName", but a key of type "{1}" was found.
WSWS3727E: Error: The java.util.HashMap stored as the "{0}" property contained a null value.
WSWS3728E: Error: The java.util.HashMap stored as the "{0}" property contained a value of type "{1}".
WSWS3729E: Error: The java.util.HashMap stored as the "{0}" property should contain null values.
WSWS3730E: Error: SOAP header "{0}" is restricted from client access.
WSWS3731E: Internal Error: the request SOAP header HashMap should have been previously validated.
WSWS3732E: Error: This DOM 3 API, method {0} of interface {1}, is not supported.
WSWS3733W: Warning: The -deployScope option is ignored unless the -role option is "develop-server" or "server".
WSWS3734W: Warning: Exception caught from invocation to {0}:
WSWS3735E: Error: The XML Schema "extension" within a "redefine" is not currently supported.
WSWS3736I: Info: SSL connection info is {0} .
WSWS3737I: Info: Found programmatically set SSL thread properties = {0} with listener = {1} registered.
WSWS3738I: Info: Found SSL configuration alias = <{0}> and SSL certificate alias = <{1}> from the message context.
WSWS3739W: Warning: Unable to resolve for an SSL configuration. Explicitly request JSSE properties from security"s JSSEHelper.
WSWS3740E: Error: No SSL configuration is available for endpoint - {0}
WSWS3741I: Info: JSSEHelper from Security returns SSL properties = {0} with listener = {1} registered.
WSWS3742I: Info: Mark SSL configuration object {0} to be deleted.
WSWS3743I: Info: Outbound connection object {0} for address {1} has been invalidated.
WSWS3744I: Info: With matching address {0}, found the associated connection object {1} to be invalidated.
WSWS3745I: Info: Return an outbound connection object: {0} that is in invalid state.
WSWS3746W: Warning: Caught {0}. Query again from the Unified Clustering Framework.
WSWS3747W: Warning: Second query from the Unified Clustering Framework failed. No
ChannelTarget object is returned from the Unified Clustering Framework.
WSWS3748I: Info: Returned ChannelTarget object from the Unified Clustering Framework: {0}
WSWS3749I: Info: Loading Document at: {0}, Attempt {1}
WSWS3750W: Warning: Class: {0}, is of type java.util.Collection.
This is NOT a supported JAX-RPC type, however generation will NOT be suspended.
WSWS3751E: Error: The ServiceName in the WSADDRESSING_DESTINATION_EPR {0} does not
match the service originally configured {1}
WSWS3752I: (C) COPYRIGHT International Business Machines Corp. 1997, 2010.
WSWS3753I: IBM WebSphere Application Server Release 8.0
WSWS3754I: Web services Java2WSDL emitter.
WSWS3755I: Web services WSDL2Java emitter.
WSWS3756E: Invalid HTTP host value. Host value is {0} within the given URL {1}
WSWS3757E: Invalid HTTP port value. Port value is {0} within the given URL {1}
WSWS3758I: Local cell name: {0}. Mapped cell name from DWLM client: {1}.
WSWS3759E: {0} encountered. Failed to evaluate the WS-Addressing EPR.
WSWS3760I: A re-directed asynchronous delivery is detected. Switch to sendSOAPRequestAsync() for {0}
WSWS3761I: Connection object: {0} will be returned later in the callback object: {1} due to an asynchronous
delivery.
WSWS3762I: A response has been received for the previous asynchronous delivery using: {0} and {1}
WSWS3763E: An error has been received in the previous asynchronous delivery using: {0} and {1}
WSWS3764E: Error: The PortName in the WSADDRESSING_DESTINATION_EPR {0} does not
match the port originally configured {1}
WSWS3765W: Warning: The substitution group reference in the schema construct named {0} will be ignored by WSDL2Java.
WSWS3766W: Warning: The argument "{0}" for the elementFormDefault option is invalid. Valid arguments are <qualified | unqualified>. Java2WSDL will ignore this option.
WSWS3767W: Warning: The argument "{0}" for the attributeFormDefault option is invalid. Valid arguments are <qualified | unqualified>. Java2WSDL will ignore this option.
WSWS3768W: Warning: The WSDL2Java emitter has found relative namespace: {0}

in the WSDL or schema file. Relative namespaces are neither WS-I compliant, nor compliant

in usage with WS-Security with digital signatures due to C14N restrictions.
WSWS3769W: Unkown option: "{0}". This entry will be ignored.
WSWS3770W: Warning: WSDL2Java does not support {0} binding namespace.
WSWS3938E: The message is enclosed in {0} tags. As stated in the Basic Profile 1.1 Specification Rule R9980 , the message must be in a SOAP Envelope.
WSWS3939E: The JMS endpoint URL is missing one or more of the following required properties: jndiConnectionFactoryName, targetService
WSWS3940E: The endpoint address URL is not of JMS type.
WSWS3941E: The destination name is missing within the JMS endpoint URL: "{0}"
WSWS3942I: The SOAPMessage getSOAPHeader or getSOAPBody method threw an exception because that message part was null. If you would rather have a null returned rather than an exception thrown you may do either of the following: 1) Use SOAPMessage.getSOAPPart().getEnvelope().getHeader() or .getBody() as appropriate, or 2) set the System Property com.ibm.websphere.webservices.soap.enable.legacy.get.behavior to true to have the SOAPMessage methods return null rather than throwing an exception.
WSWS4001E: The SOAP address should have the form http|https://host:port. An improperly formatted SOAP address was supplied for Module {0}. The incorrect SOAP address is {1}.
WSWS4002E: The router module for module {0} could not be found.
WSWS4003E: The router module for EJB module {0} is {1}. The router module"s web.xml file is missing a URL pattern for port component {2}
WSWS4004E: The wsdl-file {1} for module {0} was not found in the module.
WSWS4005E: An exception occurred while adding URL prefixes to the published WSDL file. The exception is {0}
WSWS4006E: WSWS406E the JMS URL prefix {0} is not correctly formatted. The JMS URL prefix must start with jms:/[queue|topic]?, and the destination and connectionFactory must not contain java:comp
WSWS4007E: Can not retrieve application metadata for application{1}, exception:{0}
WSWS4008E: Error: {0}
WSWS4009E: The Web service binding file, {1}, does not contain a {0} element.
WSWS4010E: An error occurred initializing the WSDL zip files. Check the log for more information.
WSWS4011E: An error occurred preparing or initializing one or more of the follwing WSDL zip file names: {0}
WSWS4012E: The WSDL zip file contains no ports. Check the log for more information.
WSWS4050E: Transform error occurred: {0}
WSWS4051E: This application might not contain the Web services deployment descriptor information you need.
WSWS4052E: No input stream obtained for the deployment descriptor.
WSWS4053E: Could not load deployment descriptor through the user workspace. Exception: {0}
WSWS4054E: Unable to transform. No resource type specified to transform.
WSWS4055E: No output stream obtained for the deployment descriptor.
WSWS4056E: A SAX parser exception occurred.
WSWS4057E: A SAX parser configuration exception occurred.
WSWS4100E: Method {0} of class {1} is not supported in SAAJ 1.2.
WSWS4101E: Method {0} of class {1} is not supported in SAAJ 1.2 and DOM Level 2.
WSWS4102E: The {0} is not available with the Dynamic SOAP protocol.
WSWS4103E: Method {0} of class {1} is only valid for messages that use the SOAP 1.2 Protocol.
The current message uses the {2} protocol.
WSWS4104E: A {0} is not supported by SAAJ 1.2.
WSWS4105E: The iterator returned from the {0} method does not support the remove() method.
WSWS4106E: The Fault Reason node does not have a Text node that matches the Locale {0}.
WSWS4107E: A Fault Reason node was expected, but was not found while invoking method {0}
WSWS4108E: A Fault Code node was expected, but was not found while invoking method {0}
WSWS4109E: MessageFactory.createMessage() when the protocol is "Dynamic Protocol".
WSWS4110E: The {0} method is not available with the Dynamic SOAP protocol.
WSWS4111E: Namespace {0} is not valid with protocol {1}.
WSWS4112E: {0} is not recognized SOAP Protocol.
WSWS4113E: {0} is not supported on a {1} object.
WSWS4114E: The SOAPBody.extractContentAsDocument() method failed because
the body contains {0} elements.
WSWS4115E: The message has an CONTENT_TYPE of {0}. A CONTENT_TYPE of {1} or {2} was expected.
WSWS4116E: An attempt was made to invoke SOAPElement.addChildElement(name, prefix) with a prefix that
was not bound to a namespace. The prefix is {0} and the name is {1}.
WSWS4117E: An attempt was made to add an SOAPEnvelope with a protocol of {0} to a SOAPMessage with a protocol of
{1}.
WSWS4118E: An attempt was made to get data from an attachment that does not have a data handler.
The attachment content id is {0}.
WSWS4119E: An attempt was made to set a {0} that was not namespace qualified.
The {0} localName is {1}; prefix is {2}: namespace is {3}.
WSWS4120E: An attempt was made to set an invalid Fault Code.
The faultCode localName is {0}; namespace is {1}.
WSWS4121E: Could not locate the endpoint for {0}.
WSWS4122I: The endpoint is currently stopped for {0}.
WSWS4123E: Could not locate the Endpoint Manager MBean for {0}.
WSWS4124E: The required "{0}" property was not present in the inbound JMS request message.
WSWS4125E: The required "{0}" property was wrong in the inbound JMS request message.
WSWS4126E: The required "{0}" property was not present in the inbound JMS request message.
WSWS4127E: The required "{0}" property was not present in the inbound JMS request message.
WSWS4128E: The required "{0}" property was wrong in the inbound JMS request message.
WSWS4129W: Could not locate the endpoint manager for the JMS target service {0}.
WSWS5001E: {0} is null.
WSWS5002E: Input parameter {0} was passed in as null, but {1} was not called.
WSWS5003E: Error {0} occurred while retrieving method {1} from class {2}: {3}
WSWS5004E: Error {0} occurred 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: Error {0} occurred while attempting to locate the following JNDI name: {1}

{2}
WSWS5008E: An error occurred while trying to obtain an InitialContext object: {0}.
WSWS5009E: Error {0} occurred while attempting to create a protocol-specific Call object: {1}
WSWS5010E: Error: Cannot find port: {0}
WSWS5011E: Method {0} is not supported in a managed environment.
WSWS5012E: An error occurred while loading a generated Stub class {0}: {1}
WSWS5013E: No constructor with the signature {0}
was found for generated Stub class {1}: {2}
WSWS5014E: An error occurred instantiating the 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: An error occurred while reading the WSDL definition that is located at URI: {0}
WSWS5018E: Error {0} occurred while trying to invoke method {1} from class {2}: {3}
WSWS5019E: An error occurred obtaining Service for port {0}: {1}
WSWS5020E: An error occurred obtaining Stub class {0}: {1}
WSWS5021E: An error occurred obtaining port {0}: {1}
WSWS5022E: An error occurred while trying to create an extension for parent type {0}
and element type {1}.
WSWS5023E: The protocol used in endpoint location URI {0} is not valid.
WSWS5024E: Missing an equals sign (=) in the query string within the endpoint location URI: {0}
WSWS5025E: The attribute name {0} is not valid.
WSWS5026E: Internal error: Duplicate shadow registry.
WSWS5027E: The property name for Call object {0} is not valid.
WSWS5028E: Error {0} occurred while trying to close a transport: {1}
WSWS5029E: Error {0} occurred while processing a method invocation: {1}
WSWS5030E: Method {0} is not valid.
WSWS5031E: The service endpoint interface {0} is not valid. No WSDL definition is available.
WSWS5032E: The service endpoint interface {0} is not valid. No default port is 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: An error occurred while getting the protocol from endpoint location URI: {0}
WSWS5042E: The protocol that is found in the WSDL endpoint location URI is not valid.
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}: An empty port name was found in the WSDL port names array.
WSWS5046E: Error {0} occurred getting an enterprise bean class name from endpoint location URI {1}: {2}
WSWS5047E: Error {0} occurred getting properties from endpoint location URI {1}: {2}
WSWS5048E: The {0} property is missing from endpoint location URI {1}.
WSWS5049E: An error occurred while trying to instantiate
a target object of class {0}: {1}
WSWS5050E: Error {0} occurred while trying to initialize
target object of class {1}: {2}
WSWS5051E: Error {0} occurred while trying to load target object class {1}: {2}
WSWS5052E: Error {0} occurred while getting the implementation class name from endpoint location URI {1}: {2}
WSWS5053E: Error {0} occurred while trying to get method {1} on target class {2}: {3}
WSWS5054E: Error {0} occurred while trying to invoke method {1} on target class {2}: {3}
WSWS5055E: Cannot find a Service for namespace {0}.
WSWS5056E: A dynamic proxy cannot be created due to exception: {0}
WSWS5057E: No PortType exists in the WSDL defintion for the specified
service endpoint interface: {0}.
WSWS5058E: The service endpoint interface {0} is not a valid interface.
WSWS5059E: Parameter of type {0} could not be serialized while trying to invoke method {1} on target class {2}
WSWS6000E: Error: {0}
WSWS6001E: Received request {0} for unregistered system service endpoint {1}.
WSWS6002E: No system endpoint router is defined for request {0}.
WSWS6003I: The SOAP Container Service is initialized.
WSWS7001I: The Axis2 service has been started.
WSWS7002E: The following exception occurred: {0}
WSWS7003E: The system encountered an internal error: {0}
WSWS7004E: The Performance Monitoring Infrastructure (PMI) services cannot be correctly loaded
for the {0} application module.
WSWS7005E: The Performance Monitoring Infrastructure (PMI) services cannot be correctly unloaded
for the {0} application module.
WSWS7006E: The {0} component could not be initialized because of the following error: {1}
WSWS7007E: The {0} application module cannot be loaded correctly because of the following error: {1}
WSWS7008E: The {0} application module cannot unload correctly because of the following error: {1}
WSWS7009E: A configuration could not be correctly created for the {0} application module.

The following error occurred: {1}
WSWS7010E: The {0} application module contains an ibmservices.xml file. This file is
not used to configure Web services.
WSWS7011E: The configuration for the {0} application module cannot load correctly.

The following error occurred: {1}
WSWS7012E: The {0} component cannot be correctly started because of the following error: {1}
WSWS7013E: The WebContainer service cannot be retrieved for the {0} component.
WSWS7014E: The VariableMap service cannot be retrieved for the {0} component.
WSWS7015E: The Repository service cannot be retrieved for the {0} component.
WSWS7016E: The Quality of Service (QoS) modules cannot load correctly on the server
because of the following error: {0}
WSWS7017E: The Quality of Service (QoS) modules did not load correctly on the
client because of the following error: {0}
WSWS7018E: The {0} Axis2 global configuration file cannot load correctly because
of the following error: {1}
WSWS7019E: The {0} module configuration file cannot load correctly.
WSWS7020E: The configuration files for Quality of Service (QoS) modules could not be
correctly located because of the following error: {0}
WSWS7021E: A Quality of Service (QoS) module could not be correctly loaded because of the
following error: {0}
WSWS7022E: The Quality of Service (QoS) configuration files for the application module
cannot load correctly from the file list because of the following error: {0}
WSWS7023W: The Quality of Service (QoS) module cannot load correctly because of a null URL.
WSWS7024E: The id attribute of the plug-in element for the ThreadContextMigrator
extension does not have an assigned value.
WSWS7025E: The {0} class did not implement the ThreadContextMigrator interface.
WSWS7026E: The ""ThreadContextMigrator"" plug-ins cannot load correctly
because of the following error: {0}
WSWS7027E: JAX-WS Service Descriptions could not be correctly built because of the following error: {0}
WSWS7028E: The Axis Object Model (OM) structure could not be built from the web.xml file
because of the following error: {0}.
WSWS7029E: A URL could not be established for the Web service because of the following
error: {0}
WSWS7030E: The {0} AxisService does not contain an implementation class name.
WSWS7031E: The {0} application module did not process correctly because of the following error: {1}
WSWS7032E: The {0} servlet contains more than one servlet mapping, which is a violation
of the JSR 109 specification.
WSWS7033E: The {0} AxisService does not contain {1} parameter.
WSWS7034E: The Performance Monitoring Infrastructure (PMI) Handler cannot be invoked
because of the following error: {0}
WSWS7035E: The {0} metadata file could not be found.
WSWS7036E: The {0} Web Services Description Language (WSDL) file cannot be located
because of the following error: {1}
WSWS7037I: The {0} URL pattern was configured for the {1} servlet located in the {2} web module.
WSWS7038E: The Axis Configuration for the {0} application module is null.
WSWS7039E: Policy sets could not be loaded correctly into the Axis Configuration
for service {0} because of the following error: {1}
WSWS7040E: In the {1} class, the {0} service name specified by the @WebServiceClient
annotation cannot be found in the {2} Web Service Description Language (WSDL) file.
WSWS7041E: The @WebServiceClient annotation of the {0} class contains an incorrect value
and the following error occurred: {1}
WSWS7042E: The {0} class was declared as an implementation of
the Axis2ServiceConfigPlugin interface, but the class does not implement the interface.
WSWS7043E: The ""Axis2ServiceConfigPlugin"" plug-ins cannot load correctly
because of the following error: {0}
WSWS7044E: The Axis2 runtime objects cannot be configured using the
Axis2ServiceConfigPlugin implementation {0}: {1}
WSWS7045E: The ConfigurationContext for the {0} application module cannot be
created correctly because of the following error: {1}
WSWS7046E: The {0} class cannot load correctly because of the following error: {1}
WSWS7047E: The URL for the {0} super class cannot load correctly because of the
following error: {1}
WSWS7048E: The {0} cache file cannot be created correctly because of the following error: {1}
WSWS7050E: The {0} cache file cannot be loaded correctly because of the following error: {1}
WSWS7051E: The {0} cache file cannot be saved correctly because of the following error: {1}
WSWS7052E: The {0} generated WSDL file could not be read correctly because of the
following error: {1}
WSWS7053E: A generated schema file could not be read correctly because of the
following error: {0}
WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the
{0} Web service implementation class because of the following error: {1}
WSWS7055E: The {0} Web Services Description Language (WSDL) file specified by annotations in
class {1} cannot be loaded correctly due to the following error: {2}
WSWS7056E: The {0} schema file cannot be displayed because of the following error: {1}
WSWS7057E: The client ConfigurationContext could not be saved correctly because of
the following error: {0}
WSWS7058E: A JAXBContext could not be created correctly because of the following error: {0}
WSWS7059E: The {0} class cannot load correctly when creating a JAXBContext.
WSWS7060E: A ClassLoader could not be found to create a JAXBContext
for the package name: {0}
WSWS7061E: The {0} Web service client could not be processed.
WSWS7062E: The {0} Web Services Description Language (WSDL) file referenced
by the @WebServiceClient annotation in the {1} class could not be loaded.
WSWS7063E: An error occurred when determining if an unknown endpoint is processable
using the UnknownEPRResolverPlugin implementation {0}: {1}
WSWS7064E: The configuration context for an unknown endpoint cannot be retrieved
using the UnknownEPRConfigCtxtLoaderPlugin implementation {0}: {1}
WSWS7065E: The {0} Web service implementation class refers to the absolute Web Services
Description Language (WSDL)location {1} using annotations.
WSWS7066E: The {0} Web Services Description Language (WSDL) file cannot be displayed due to
the following error: {1}
WSWS7067E: The {0} Servlet cannot specify the * character as a URL pattern.
WSWS7068I: The thread {0} is waiting for notification.
WSWS7069I: Current pool size: {0}. Connections-in-use size: {1}. Configured pool size: {2}
WSWS7070I: A cookie was received for the {0} HTTP header in the response from
the connection to: {1}
WSWS7071I: Loading ssl.client.props {0}
WSWS7072I: Found programmatically set SSL thread properties = {0}
with listener = {1} registered.
WSWS7073I: Found SSL configuration alias = {0} and SSL certificate
alias = {1} from the message context.
WSWS7074W: The SSL configuration could not be correctly resolved. The system will
explicitly request the JSSE properties from the security"s JSSEHelper.
WSWS7075I: The JSSEHelper from security returns the {0} SSL properties
with listener = {1} registered.
WSWS7076I: The {0} listening host and port {1} have been associated.
WSWS7077I: The {0} Endpoint Reference (EPR) has been established.
WSWS7078I: Virtual host returned by {0}: {1}
WSWS7079I: The Dynamic Work Load Management Client is enabled: {0}
WSWS7080E: The following schema for HTTP is not supported: {0}
WSWS7081I: The {1} host, {2} port, and {3} URI path was mapped to the {0} cluster.
WSWS7082I: Local cell name: {0}. Mapped cell name from DWLM client: {1}.
WSWS7083W: The Web services engine will attempt to query again from
the Unified Clustering Framework, due to the following error: {0}
WSWS7084W: A second query from the Unified Clustering Framework has failed. No
ChannelTarget object is returned from the Unified Clustering Framework.
WSWS7085I: The {0} ChannelFramework EndPoint object is mapped, using the
Identity object of {1}
WSWS7086I: The {0} outbound connection object has expired. The elapsed time from the
last access to the object is {1} millieseconds.
WSWS7087E: An integrity problem occurred with the connection pool.
WSWS7088I: The {0} current thread is going to wait {1} milliseconds for notification.
WSWS7089I: The connection wait has timed out.
WSWS7090I: The channel buffer size is {0}.
WSWS7091E: The following errors occurred on the channel framework service: {0}
WSWS7092E: The HTTP(S) proxy information for the proxy connection was not received.
WSWS7093W: The HTTP response redirected the target resource to a new location: {0}
WSWS7094E: An incorrect {0} HTTP host value was specified within the URL {1}
WSWS7095E: An incorrect {0} HTTP port value was specified within the URL {1}
WSWS7096E: An unsupported HTTP version is found: {0}
WSWS7097E: The {0} parameter can have values of only HTTP/1.0 or HTTP/1.1
WSWS7098E: Both the TransportOut and property MessageContext.TRANSPORT_OUT values are null.
WSWS7099E: The attachment was not correctly deleted due to the following error: {0}
WSWS7100E: {0} has not been set.
WSWS7101W: A connection is attempted with an outbound connection
object that is already marked to be closed: {0}
WSWS7102I: The {0} MessageContext object could not be found.
WSWS7103I: The required asynchronous response servlet is not available.
WSWS7104I: The asynchronous response servlet was not correctly initialized due to the following error: {0}
WSWS7105I: The context ID {0} was received from an unknown asynchronous response.
WSWS7106I: The port {0} is not valid.
WSWS7107I: The host address {0} has not been established yet. An endpoint reference (EPR)
cannot be generated.
WSWS7108W: The {0} attribute is not valid.
WSWS7109E: The {0} unmarshaled object is not a policy object.
WSWS7110E: The policy file was not successfully validated due to the following error: {0}
WSWS7111E: The policy file was not marshaled correctly due to the following error: {0}
WSWS7112E: The {0} element received an object that is not a string object.
WSWS7113E: A non {0} object was received for the {1} element.
WSWS7114E: An Axis2 MessageContext object was not found in the AsyncResponseContext object.
WSWS7115E: The required AsyncResponseServlet is not available.
WSWS7116E: An exception occurred in the asynchronous getRequestBodyBuffers(): {0}
WSWS7117E: An exception occurred in the synchronous getRequestBodyBuffers(): {0}
WSWS7118E: An exception occurred in the discriminate method: {0}
WSWS7119E: An exception occurred during an asynchronous read operation: {0}
WSWS7120E: An exception occurred when performing asynchronous operations: {0}
WSWS7121E: No HTTP status has been received for the current HTTP response.
WSWS7122E: This request is not a one-way request and should have yielded a response from {0}.
WSWS7123E: No HTTPConnection object was returned from the outbound connection pool.
WSWS7124E: The transport header key is not valid.
WSWS7125E: The transport header value with key {0} is not valid.
WSWS7126E: The server module metadata in the Axis servlet for the {0} module could not
be retrieved.
WSWS7127E: The configuration context in the Axis servlet for the {0} module could not
be retrieved.
WSWS7128E: The acknowledgement was not correctly sent due to the following error: {0}.
WSWS7129E: The Secure Sockets Layer (SSL) client configuration file, ssl.client.props,
is not specified due to the following error: {0}
WSWS7130E: No Secure Sockets Layer (SSL) configuration is available for the {0} endpoint.
WSWS7131E: The ""ApplicationContextMigrator"" plug-ins cannot load correctly
because of the following error: {0}
WSWS7132E: The id attribute of the plug-in element for the ApplicationContextMigrator
extension does not have an assigned value.
WSWS7133E: The {0} class did not implement the ApplicationContextMigrator interface.
WSWS7134E: The ibmasyncrsp.ear system application could not be installed due to the
following error: {0}.
WSWS7135E: The following error occurred while attempting to retrieve the
com.ibm.websphere.webservices.Constants.RESPONSE_TRANSPORT_PROPERTIES property from the
response: {0}
WSWS7136E: The system could not find an OperationDescription for the Web service request.
WSWS7137W: The system could not correctly load the {0} binding file for the {1} Enterprise JavaBeans
(EJB) Java archive (JAR) file.
WSWS7138E: The system cannot locate an Enterprise JavaBeans (EJB) object. An EJB object
is expected at dispatcher cleanup.
WSWS7139E: The {0} method on the {1} class was not found.
WSWS7140E: The server cannot locate the Web service endpoint interface for an Enterprise
JavaBeans (EJB) file.
WSWS7141E: The server cannot locate an AxisService for the Web service request.
WSWS7142E: The following error occurred during the invocation of an EJB Web service: {0}
WSWS7143E: The system cannot find an enterprise bean for the Web service request.
WSWS7144E: The system could not find an OperationDescription for the {0} operation.
WSWS7145E: More than one OperationDescription was found for the {0} operation.
WSWS7146E: The server cannot retrieve the Transport map service for the {0} component.
WSWS7147E: The system could not locate the endpoint for {0}.
WSWS7148I: The endpoint is currently stopped for {0}.
WSWS7149E: The {0} ejb-link value for the {1} Enterprise JavaBeans Web service implementation class
did not correspond to an enterprise bean defined in the ejb-jar.xml file for the {2} module.
WSWS7150E: The system could not build a runtime configuration for the {0} application module because of the
following error: {1}
WSWS7151E: The {0} parameter cannot be added to the {1} annotation instance because it is not a
known parameter.
WSWS7152E: The {0} parameter cannot be obtained from the {1} annotation instance because it is not a
known parameter.
WSWS7153E: A null argument was passed to the {0} annotation processor.
WSWS7154E: The system could not retrieve the runtime configuration for the {0}
annotation processor.
WSWS7155E: The system could not correctly build JAX-RPC service descriptions because of the following error: {0}
WSWS7156E: The {0} JAX-WS Web service implementation class referred to the {1} Service Endpoint Interface (SEI) class,
but the SEI class did not have an @WebService annotation.
WSWS7157E: The {0} JAX-WS Web service implementation class referred to the {1} Service Endpoint Interface (SEI) class,
but the SEI class could not be found.
WSWS7158E: The {0} port-component element was identified as a JAX-RPC port component but was found in the {1}
webservice-description element, which also contains JAX-WS port components. Mixing JAX-RPC and JAX-WS port components within the
same webservice-description element is not allowed.
WSWS7159E: The {0} port-component in the {1} webservice-description was identified as a JAX-RPC port component,
but it did not contain a value in the service-endpoint-interface element.
WSWS7160E: The {0} port-component in the {1} webservice-description was identified as a JAX-RPC port component,
but the {2} SEI class specified by the service-endpoint-interface element contained the @WebService annotation.
WSWS7161E: The {0} namespace URI was specififed for the {1} port, but this does not correspond to the {2} target
namespace URI for the {3} JAX-WS Web service implementation class.
WSWS7162E: The target URL is not correctly defined.
WSWS7163E: The JMS endpoint URL is missing one or more of the following required properties:
connectionFactory, destination, targetService.
WSWS7164E: Two-way requests are not supported for topic destinations.
WSWS7165E: The request wait has timed out.
WSWS7166E: The reply message correlation ID does not match with the request message ID.
WSWS7167E: The input stream of the reply message is not correctly processed.
WSWS7168E: The message type is not valid for the reply message.
WSWS7169E: The MessageContext was not created correctly.
WSWS7170E: The TargetService is not in the correct format.
WSWS7171E: The system cannot find the configuration for the JMS request.
WSWS7172E: The system encountered a JMS exception: {0}
WSWS7173E: The system encountered the following exception: {0}
WSWS7174E: The {0} JNDI InitialContext object was not created.
WSWS7175E: The system encountered an naming exception during a JNDI operation: {0}
WSWS7176E: The following exception is encountered in the {0} property in the JMS URL {1}
WSWS7177E: The system encountered an AxisFault: {0}
WSWS7178E: The transport header key in the JMS request message cannot be processed.
WSWS7179E: The system encountered the following exception during request processing: {0}
WSWS7181E: The system encountered the following exception when sending the reply message: {0}
WSWS7190E: The request message does not include a SOAP message.
WSWS7191E: The response message does not include a SOAP message.
WSWS7192E: An error occurred attempting to configure the WSDL Reader: {0}
WSWS7193E: An error occurred attempting to annotate WSDL definition for the {0} service: {1}
WSWS7194E: An EndpointLifecycleManager instance was not successfully created.
WSWS7195E: The metadata for the {0} service reference was not found.
WSWS7196E: The {0} service reference on the {1} member in the {2} class specifies the {3} service-ref-type class but
other metadata was found for this service reference which specifies the {4} service-ref-type class.
WSWS7197E: The {0} service reference on the {1} member in the {2} class specifies the {3} service-interface class but
other metadata was found for this service reference which specifies the {4} service-interface class.
WSWS7198E: The @HandlerChain annotation specified for the {0} service reference on the {1} member in the {2} class
specifies the {3} name value. This conflicts with the {4} name value that was specified for handler chain information previously associated
with this service reference.
WSWS7199E: The @HandlerChain annotation specified for the {0} service reference on the {1} member in the {2} class
specifies the {3} file value. This conflicts with the {4} file value that was specified for handler chain information previously associated
with this service reference.
WSWS7200E: The @WebServiceRef or @Resource annotation on the {0} class does not specify a value for the name or type attribute. For @WebServiceRef
or @Resource annotations found at the class level, the name and type attributes are required.
WSWS7201E: The @WebServiceRef annotation was found on the {0} class, but the type attribute and the value
attribute do not specify the same class. If the @WebServiceRef annotation indicates a service type injection, and the value attribute
does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same.
WSWS7202E: An @WebServiceRef or @Resource annotation was found on the {0} method in the {1} class, but the method does not follow the standard
JavaBeans convention.
WSWS7203E: The @WebServiceRef or @Resource annotation was found on the {0} member in the {1} class but the type of injection could not be inferred
from either the type attribute or the member type.
WSWS7204E: The @WebServiceRef annotation was found on the {0} member in the {1} class, but the {2} class specified by the value
attribute was not a subclass of javax.xml.ws.Service. If an @WebServiceRef annotation is used for injection of a port, the value attribute
must specify a class that is a subclass of javax.xml.ws.Service.
WSWS7205E: The @WebServiceRef or @Resource annotation was found on the {0} member in the {1} class, but the type attribute specifies the
{2} class that is not compatible with the {3} class of the annotated member.
WSWS7206E: The @WebServiceRef annotation was found on the {0} member in the {1} class, but the type attribute and the value
attribute do not specify the same class. If the @WebServiceRef annotation indicates a service type injection, and the value attribute
does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same.
WSWS7207E: The @WebServiceRef annotation was found on the {0} member in the {1} class, but the value attribute did not specify
a class that is a subclass of the javax.xml.ws.Service class. If the @WebServiceRef annotation is used to indicate port injection, the value
attribute must specify a class that is a subclass of the javax.xml.ws.Service class.
WSWS7208E: The @WebServiceRef annotation was found in the {1} class, but the {2} class specified by the value attribute was not
a subclass of javax.xml.ws.Service. If the @WebServiceRef type attribute specifies an service endpoint interface (SEI) class, the value attribute must specify a subclass of
javax.xml.ws.Service.
WSWS7209W: The {0} service reference in the {1} module is missing either the service QName or WSDL file location attribute.
This may cause unpredictable results when this service reference is requested.
WSWS7210E: The {0} internal service class was not found.
WSWS7211E: The {0} application client file was not processed due to the following error: {1}
WSWS7212E: A {0} class-level service reference was found which specifies the {1} service-ref-type class but another
service reference was found which specifies the {2} service-ref-type class.
WSWS7213E: A {0} class-level service reference was found which specifies the {1} service-interface class but another
service reference was found which specifies the {2} service-interface class.
WSWS7214E: The @HandlerChain annotation specified for the {0} class-level service reference specifies the {1} name value.
This conflicts with the {2} name value that was specified for handler chain information previously associated with this service reference.
WSWS7215E: The @HandlerChain annotation specified for the {0} class-level service reference specifies the {1} file value.
This conflicts with the {2} file value that was specified for handler chain information previously associated with this service reference.
WSWS7216E: The following error occured during a JNDI lookup operation for the {0} connection factory : {1}
WSWS7217E: The following error occurred while starting the JMS Async Response Message Listener: {0}
WSWS7218E: The following error occurred while stopping the JMS Async Message Listener: {0}
WSWS7219I: The {0} context ID was received from an unknown asynchronous response.
WSWS7220E: A JAX-WS handler instance was not created because the handler class is null.
WSWS7221E: An instance of the {0} JAX-WS handler class was not created due to the following error: {1}.
WSWS7222E: Injection targets were not retrieved due to the following error: {0}.
WSWS7223E: The module metadata was not available after injection meatdata was created.
WSWS7224E: The {0} service reference in the {1} module was identfied as a JAX-WS style service-reference, but the service-interface
element specifies the {2} class that is not a subclass of javax.xml.ws.Service.
WSWS7225E: The {0} service reference in the {1} module specifies a javax.xml.ws.Service class type in the
service-interface and service-ref-type elements, but the class names do not match. If both element types specify a javax.xml.ws.Service
class type, they must specify the same class.
WSWS7226E: The {0} service reference in the {1} module was identfied as a JAX-RPC style service-reference, but the service-interface
element specifies the {2} class which is not a subclass of javax.xml.rpc.Service.
WSWS7227E: No methods were found for the {0} Enterprise JavaBeans (EJB) Web service endpoint class.
WSWS7228E: The required {0} property in the inbound JMS request message is incorrect.
WSWS7229E: The required {0} property is missing in the inbound JMS request message.
WSWS7230E: The required {0} property is missing in the inbound JMS request message.
WSWS7231E: The required {0} property is incorrect in the inbound JMS request message.
WSWS7232E: A response was not written to the output stream because a message formatter was not found.
WSWS7233E: The {0} JAX-WS application handler class did not load correctly because of the following error: {1}.
WSWS7234E: The {0} class was specified as a JAX-WS application handler, but it is not a javax.xml.ws.handler.Handler type.
WSWS7235E: The {0} web service implementation in an Enterprise JavaBeans module could not be invoked because a target method could not be found.
WSWS7236E: Internal error. A response from a web service endpoint in an Enterprise JavaBeans module could not be processed because an endpoint manager
could not be located.
WSWS7237E: Internal error. An instance of the {0} web service implementation class could not be located.
WSWS7238E: Web service references specified in the {0} module in the {1} application could not be correctly processed due to the following error {2}.
WSWS7239E: The web service metadata for the {0} module in the {1} application could not be processed correctly due to the following error {2}.
WSWS7240E: Annotation metadata for the @Resource or @WebServiceRef annotation in the {0} class could not be merged due to the following error: {1}
WSWS7241E: Annotation metadata for the @Resource or @WebServiceRef annotation on the {0} member in the {1} class could not be merged due to the following error: {2}
WSWS7242E: An @Resource annotation was found in the {0} class that specified a JAX-RPC service reference but a service-ref with
the {1} service-ref-name value was not defined in the deployment descriptor.
WSWS7243E: Validation of the @Resource or @WebServiceRef annotation in the {0} class failed due to the following error: {1}
WSWS7244E: Validation of the @Resource or @WebServiceRef annotation on the {0} member in the {1} class failed due to the following error: {2}
WSWS7245E: An @Resource or @WebServiceRef annotation on the {0} member in the {1} class specifies the {2} type which is not compatible with
the {3} type targetted for injection.
WSWS7246E: An @Resource or @WebServiceRef annotation was found on the {0} field in the {1} class, but the field is declared as final. This is not allowed by the
Java Enterpise Editon 5 Platform Specification.
WSWS7247E: An @WebServiceRef annotation was found on the {0} class but neither the type nor the value attribute referred to a javax.xml.ws.Service
class type. Either the type or value attribute must refer to a java.xml.ws.Service class type.
WSWS7248E: An @WebServiceRef annotation was found on the {0} member in the {1} class but neither the type nor the value attribute referred to a
javax.xml.ws.Service class type. Either the type or value attribute must refer to a java.xml.ws.Service class type.
WSWS7249E: Could not find the Endpoint Manager MBean for the application {0}, module {1}.
WSWS7250E: Web service metadata for the JAX-WS Web service cannot be completed because the {0} class indicated by a deployment descriptor in the
{1} module cannot be located.
WSWS7251E: The {0} ejb-link value was specified by the {1} port-component in the webservices.xml within the {2} module, but an enterprise bean with that
name was not found.
WSWS7252E: The {0} servlet-link value was specified by the {1} port-component in the webservices.xml within the {2} module, but a servlet with that
name was not found.
WSWS7253E: The {0} service-endpoint-interface class specified by the webservices.xml in the {1} module cannot be located.
WSWS7254E: Client binding information for the {0} module in the {1} application could not be processed due to the following error: {2}.
WSWS7255E: Client binding information for the {0} application could not be processed due to the following error: {1}.
WSWS7256E: The {0} custom handler did not define a phase, or it defined a phase which is not allowed for custom handlers.
WSWS7257E: Some operations for service {0} do not have a configured SSL policy set.
WSWS7258E: Web Services Description Language (WSDL) files for the {0} module will not be generated due to
the following error: {1}
WSWS7259E: The {0} service-endpoint-interface class was defined in the webservices.xml for the {1} JAX-WS implementation
class, but an @WebService annotation was not found on the service-endpoint-interface class.
WSWS7260E: The system encountered an error retrieving the inbound request content length.
WSWS7261E: Web services configuration information was not available for an incoming request.
WSWS7262E: Web services metadata cache could not be generated for the {0} application due to the following error: {1}.
WSWS7263E: The following exception occured: {0}

The previous error might have been caused by a lack of system resources due to server is too busy processing multiple requests.
WSWS7264E: The @WebServiceRef annotation incorrectly specified the "lookup" attribute in addition to other attributes.
WSWS7265E: The previous error occurred on the @WebServiceRef annotation which was specified on the following injection target: {0}
WSWS7266E: An error occurred while processing the @WebServiceRef or @Resource annotation which was specified on the following injection target: {0}
WSWS7270W: Transport property {0} is invalid and cannot be processed.
WSWS7271E: The JMS endpoint URL is missing one or more of the following required properties:
jndiConnectionFactoryName, targetService.
WSWS7272E: The endpoint address URL is not of JMS type.
WSWS7273E: The required {0} property was not present in the inbound JMS request message.
WSWS7274E: The inbound JMS request URL is not in the correct format.
WSWS7275E: The inbound JMS request URI {1} contains target Service {0}.
WSWS7276E: The charset {0} in contentType header does not match with XML encoding statement {1} sent to the request queue.
WSWS7277E: A Non-integer value, [{0}], is defined for the [{1}] custom property in the HTTP transport configuration.
WSWS7278E: The Simple and Protected GSS-API Negotiation (SPNEGO) feature is enabled with the [{0}] custom property in the HTTP transport configuration, but the [{0}] custom property is either missing or empty.
WSWS7279E: The value [{0}] for the [{1}] custom property in the HTTP transport configuration is not valid. The valid values are [{2}].
WSWS7280E: The Simple and Protected GSS-API Negotiation (SPNEGO) login mechanism is set to [{0}], but there is no basic authentication user name specified in the HTTP transport configuration.
WSWS7281E: The Simple and Protected GSS-API Negotiation (SPNEGO) login mechanism is set to [{0}], but there is no basic authentication password specified in the HTTP transport configuration.