WSWS

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.
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}.


Terms and conditions for information centers | Feedback

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