OWS-00016 to OWS-60003

25 OWS-00016 to OWS-60003

OWS-00016: no method to retrieve the daylight savings offset (getDSTSavings) defined on TimeZone
Category:: WebService
Cause:: Oracle did not find a method for setting daylight savings time for the default timezone on this system.
Action:: Check that default timezone is set correctly. Check that the Java Runtime Environment(TM) (JRE) that is used is complete.

OWS-00017: literal ArraySerializer.initialize error encountered: Exception message is {0} Stack trace is {1}
Category:: WebService
Cause:: Could not initialize Literal Array Serializer for JAXRPC databinding
Action:: System Internal Error - Contact Oracle Support Services

OWS-00018: getElementDateValue exception {0}
Category:: WebService
Cause:
Action:

OWS-00019: DOM Exception from removeElement {0}
Category:: WebService
Cause:
Action:

OWS-00020: problem found in XML parsing: {0}
Category:: WebService
Cause:
Action:

OWS-00021: Error creating XML mapping factory: {0}.
Category:: WebService
Cause:
Action:

OWS-00022: The WSDL generator can process only one service at a time. The first service is used.
Category:: WebService
Cause:
Action:

OWS-00023: could not copy {0} to {1}
Category:: WebService
Cause:
Action:

OWS-00024: {0} Failed to load dependent class: {1}
Category:: WebService
Cause:
Action:

OWS-00025: Exception converting WSDL types to XML Schema: {0}
Category:: WebService
Cause:
Action:

OWS-00028: Warning while processing WSM client configuration: {0}.
Category:: WebService
Cause:
Action:

OWS-00029: Error reading WSM client configuration file: {0}.
Category:: WebService
Cause:: The client side proprietry descriptor is invalid
Action:: Validate the client properietary descriprtor as per the schema "http://xmlns.oracle.com/oracleas/schema/11/oracle-webservices-client-11_1.xsd"

OWS-00030: Failed to find wsm client configuration file {0}
Category:: WebService
Cause:: The user specified client side oracle webservices proprietary configuration file is missing.
Action:: Ensure the valid location of client side config file is provided or it's available in classpath

OWS-00031: Warning while processing WSM server configuration: {0}.
Category:: WebService
Cause:
Action:

OWS-00032: Error reading WSM server configuration file: {0}.
Category:: WebService
Cause:: Cannot read WSM server configuration file
Action:: Ensure given WSM configuration file(Oracle proprietry descriptor) at server side is valid

OWS-00033: Failed to find deployment descriptor file {0}
Category:: WebService
Cause:: Could not find deployment descriptor file
Action:: Ensure server side deployment descriptor file is not missing

OWS-00034: <input> element of operation "{0}" in binding "{1}" does not define name attribute. The default name "{2}" does not match the name defined in the corresponding portType section: "{3}". Add name attribute in the <input> element using same value in portType to achieve interoperability.
Category:: WebService
Cause:
Action:

OWS-00035: <output> element of operation "{0}" in binding "{1}" does not define name attribute. The default name "{2}" does not match the name defined in the corresponding portType section: "{3}" Add name attribute in the <output> element using same value in PortType to achieve interoperability.
Category:: WebService
Cause:
Action:

OWS-00036: XML fragment top level tag name "{0}" has been corrected to "{1}"
Category:: WebService
Cause:
Action:

OWS-00037: No method found in SEI: {0}
Category:: WebService
Cause:
Action:

OWS-00038: A WSDL port in the model is missing a name
Category:: WebService
Cause:
Action:

OWS-00039: The schema using the namespace of {0} may cause unexpected failures, use {1} instead.
Category:: WebService
Cause:
Action:

OWS-00040: The element {0} in the supplied deployment descriptor will be ignored.
Category:: WebService
Cause:
Action:

OWS-00043: The WSDL contains a mixture of document and rpc styles, the generated WSDL will need to be modified to work correctly.
Category:: WebService
Cause:
Action:

OWS-00044: There is no management configuration for service: {0} in supplied proprietary deployment descriptor {1}, make sure the service name is correct
Category:: WebService
Cause:
Action:

OWS-00045: {0} does not have all the getter and setter methods. Set overwriteBeans to true to allow re-generation of correct value type class.
Category:: WebService
Cause:
Action:

OWS-00046: Cannot update web.xml file, <url-pattern> {0} already exists.
Category:: WebService
Cause:: The file output/war/WEB-INF/web.xml already contains a URL pattern that the system wants to use for another servlet mapping.
Action:: Specify a unique uri argument or change the url-pattern in the existing web.xml.

OWS-00047: Could not update web.xml because <servlet-name> "{0}" already exists. The value of <servlet-name> generated by Web Services Assembler is the port name. If bottom-up assembly is used, specify a portName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files, so that they do not share deployment descriptors.
Category:: WebService
Cause:: The file output/war/WEB-INF/web.xml contained the URL and it was assigned to another servlet.
Action:: For bottom-up assembly specify a different portName. For top-down assembly or genDDs separate two Web services into different WAR files or change the name of the servlet in the web.xml file.

OWS-00048: Could not update webservices.xml because <webservice-description-name> "{0}" already exists. The value of the <webservice-description-name> generated by Web Services Assembler is always the service name. If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.
Category:: WebService
Cause:: The file output/war/WEB-INF/webservices.xml already contains a webservice-description-name. The system wants to re-use this name for a new Web service. The value of the <webservice-description-name> generated by the system is always the service name.
Action:: If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files, so that they do not share deployment descriptors.

OWS-00049: Could not update webservices.xml because <port-component-name> "{0}" already exists. The value of <port-component-name> generated by Web Services Assembler is always the port name. If bottom-up assembly is used, specify a portName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files, so they do not share deployment descriptors.
Category:: WebService
Cause:: The file output/war/WEB-INF/webservices.xml already contains a port-component-name that the system wants to use for a new port. The value of the <port-component-name> generated by the system is always the port name.
Action:: If bottom-up assembly is used, specify a portName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files, so that they do not share deployment descriptors.

OWS-00050: Could not update oracle-webservices.xml because <webservice-description> name "{0}" already exists.The name of the <webservice-description> generated by Web Services Assembler is always the service name. If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files, so they do not share deployment descriptors.
Category:: WebService
Cause:: The file output/war/WEB-INF/oracle-webservices.xml already contains a webservice-description-name that the system wants to use for a new webservice. The value of the <webservice-description-name> generated by the system is always the service name.
Action:: If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.

OWS-00051: Could not update oracle-webservices.xml because <port-component> name "{0}" already exists. The value of <port-component> name generated by Web Services Assembler is always the port name. If bottom-up assembly is used, specify a portName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.
Category:: WebService
Cause:: The file output/war/WEB-INF/webservices.xml already contains a port-component name that the system wants to use for a new port. The value of the <port-component> name generated by the system is always the port name.
Action:: If bottom-up assembly is used, specify a portName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.

OWS-00052: Could not update oracle-webservices.xml because <endpoint-address-uri> "{0}" already exists. Specify a uri argument value that does not already exist.
Category:: WebService
Cause:: The file output/war/WEB-INF/oracle-webservices.xml already contains an endpoint-address-uri that the system wants to use for a new webservice port.
Action:: Specify a uri argument value that does not already exist.

OWS-00053: The wire signature of operation by name "{0}" is same as operation by name "{1}". This does not conform to WS-I Basic Profile v1.1. R2710: The operations in a wsdl:binding in a description MUST result in wire signatures that are different from one another. An endpoint that supports multiple operations must unambiguously identify the operation being invoked based on the input message that it receives. This is only possible if all the operations specified in the wsdl:binding associated with an endpoint have a unique wire signature.
Category:: WebService
Cause:
Action:

OWS-00054: When "linkReceiveWithReplyTo" is true, either receive destination/connection-factory or reply-to destination/connection-factory must be set.
Category:: WebService
Cause:: The linkReceiveWithReplyTo argument requires the receive or reply-to arguments defined so the system can make the values the same.
Action:: Specify replyToConnectionFactoryLocation and (replyToQueueLocation or replyToTopicLocation) or specify receiveConnectionFactoryLocation and ( receiveQueueLocation or receiveTopicLocation).

OWS-00055: When "linkReceiveWithReplyTo" is true, the value of parameter "{0}" and parameter "{1}" should be same.
Category:: WebService
Cause:: When the argument linkReceiveWithReplyTo is set to true and both replyTo* and receive* arguments are specified they must have the same value.
Action:: Either remove one of the arguments shown in the message or set the arguments to the same value.

OWS-00056: JMS delivery mode "{0}" is invalid, ignore this setting.
Category:: WebService
Cause:
Action:

OWS-00057: The received SOAP fault contains non standard fault element: "{0}". This element will be ignored.
Category:: WebService
Cause:
Action:

OWS-00058: The class "{0}" exists, but could not be loaded.
Category:: WebService
Cause:
Action:

OWS-00059: Ignoring method "{1}" in SEI "{0}" because it is not JAX-RPC compliant. The reason is "{2}"
Category:: WebService
Cause:
Action:

OWS-00060: Ignoring property name "{0}" in Java exception "{1}" because it is not JAX-RPC compliant
Category:: WebService
Cause:
Action:

OWS-00061: Ignoring property name "{0}" in Java class "{1}" because it is not JAX-RPC compliant
Category:: WebService
Cause:
Action:

OWS-00062: Ignoring exception of type "{0}" in Java method "{1}" because it is not JAX-RPC compliant
Category:: WebService
Cause:
Action:

OWS-00064: Attribute "schemaLocation" is not present on a schema import element.
Category:: WebService
Cause:
Action:

OWS-00065: Interface "{0}" is not JAX-RPC compliant: it does not extend java.rmi.Remote.
Category:: WebService
Cause:
Action:

OWS-00066: Method "{0}" is not JAX-RPC compliant: it does not throw java.rmi.RemoteException.
Category:: WebService
Cause:
Action:

OWS-00067: There is no management configuration for port {0} in the supplied proprietary deployment descriptor. Ensure the port name is correct.
Category:: WebService
Cause:
Action:

OWS-00070: No matching type found for the custom type mapping with QName {0}
Category:: WebService
Cause:: A custom type has been defined in an oracle-webservices.xml file but no associated type can be found in the schemas associated with the webservice.
Action:: Remove the custom type mapping or correct the name of the custom type mapping so it matches a type in the schema.

OWS-00071: Custom type mappings for global elements are not supported. The custom type mapping with the QName of {0} will not be applied to the global element.
Category:: WebService
Cause:
Action:

OWS-00073: A failure occurred during Oracle Web Services Management agent interceptor {0} processing. {1}
Category:: WebService
Cause:: Could not process Oracle Web Services Management Agent interceptor
Action:: System Internal Error - Contact Oracle Support Services

OWS-00074: {0} does not have all the getter and setter methods. Ensure the user defined class matches type {1}.
Category:: WebService
Cause:
Action:

OWS-00075: Schema with schema namespace {0} is not supported
Category:: WebService
Cause:
Action:

OWS-00076: The service implementation class: {0} does not implement java.io.Serializable. This class is not suitable for clustered environments indicated by the argument recoverable=true.
Category:: WebService
Cause:
Action:

OWS-00077: The Value Type class: {0} does not have a valid Java Bean pattern.
Category:: WebService
Cause:
Action:

OWS-00084: Failed to find Oracle Web Services Management agent configuration {0}
Category:: WebService
Cause:: Could not find Oracle Web Services Management agent configuration file
Action:: Ensure correct location of OWSM agent configuration file is provided

OWS-00085: The schema element {0} is not supported. The type {1} uses this schema element and will be ignored.
Category:: WebService
Cause:
Action:

OWS-00086: The nested generic type {0} is not supported.
Category:: WebService
Cause:
Action:

OWS-00101: Mapped {0} to javax.xml.soap.SOAPElement.
Category:: WebService
Cause:: The system defaults to a SOAP element, since it could not determine how to map the specified schema type to a Java Bean.
Action:: Switching to a different data binding like JAXB may allow the system to create Java objects for the type.

OWS-00102: Mapped {0} to javax.xml.soap.SOAPElement{2}. Reason for not creating a custom Java type: {1}
Category:: WebService
Cause:
Action:

OWS-00103: nested model group is not supported.
Category:: WebService
Cause:
Action:

OWS-00104: namespace name constraint is not supported (except for ##any, ##other).
Category:: WebService
Cause:
Action:

OWS-00105: choice is not supported.
Category:: WebService
Cause:
Action:

OWS-00106: wildcard or element is not supported.
Category:: WebService
Cause:
Action:

OWS-00107: multiple occurrences are not supported.
Category:: WebService
Cause:
Action:

OWS-00108: simple or mixed content is not supported.
Category:: WebService
Cause:
Action:

OWS-00109: a mismatch was detected in the parent type.
Category:: WebService
Cause:
Action:

OWS-00110: an unsupported simple type.
Category:: WebService
Cause:
Action:

OWS-00111: expected a soap-enc type.
Category:: WebService
Cause:
Action:

OWS-00112: found a simple type with attributes.
Category:: WebService
Cause:
Action:

OWS-00113: mixed content was seen, this may not be a valid SOAP type.
Category:: WebService
Cause:
Action:

OWS-00114: use of an unimplemented feature.
Category:: WebService
Cause:: An unimplemented feature is used in the schema.
Action:: Avoid the unimplemented feature or use the SAAJ API to construct the XML element.

OWS-00115: the base type is not supported.
Category:: WebService
Cause:: An unimplemented feature is used in the base type definition.
Action:: Avoid the unimplemented feature or use the SAAJ API to construct the XML element.

OWS-00119: Deleting field: "{0}"
Category:: WebService
Cause:
Action:

OWS-00126: Deleting unused method: "{0}"
Category:: WebService
Cause:
Action:

OWS-00129: Changing parameter type of "{0}" from "{1}" to "{2}"
Category:: WebService
Cause:
Action:

OWS-00130: Adding new parameter "{0}"
Category:: WebService
Cause:
Action:

OWS-00131: Deleting old parameter "{0}"
Category:: WebService
Cause:
Action:

OWS-00132: Changing return type of "{0}" from "{1}" to "{2}"
Category:: WebService
Cause:
Action:

OWS-00136: Adding initializer "{0}" to field "{1}"
Category:: WebService
Cause:
Action:

OWS-00137: Removing initializer "{0}" from field "{1}"
Category:: WebService
Cause:
Action:

OWS-00138: Changing initializer of field "{0}" from "{1}" to "{2}"
Category:: WebService
Cause:
Action:

OWS-00139: The body of the method by name "{0}" could not be merged. The new method required code is "{1}"
Category:: WebService
Cause:: During top-down generation JDeveloper could not merge the generated code and modified code.
Action:: None

OWS-00140: No body expected for the method "{0}".
Category:: WebService
Cause:: During top-down generation JDeveloper found unexpected code in the Java source file provided by the user.
Action:: None

OWS-00141: HTTP transport error: {0}
Category:: WebService
Cause:: Error while getting the SOAPConnectionFactory object due to unsupported SAAJ communication infrastructure
Action:: System Internal Error - Contact Oracle Support Services

OWS-00142: local transport error: {0}
Category:: WebService
Cause:: Error occcured while processing request
Action:: System Internal Error - Contact Oracle Support Services

OWS-00143: service error: {0}
Category:: WebService
Cause:: Service Invocation failed. It might be because of an error while generating the stub implementation class or a dynamic proxy.
Action:: None

OWS-00144: not an interface: {0}
Category:: WebService
Cause:: In the createService(Class serviceInterface, QName name) method client code has provided an interface that is not a Service interface.
Action:: Ensure that the supplied interface extends javax.xml.rpc.Service

OWS-00145: cannot locate service implementation class for service: {0}
Category:: WebService
Cause:: An error occurred while generating a stub implementation class or a dynamic proxy. The service implementation class could not be found in the classpath.
Action:: Ensure that the service implementation class is available in the classpath.

OWS-00146: failed to create service implementation instance: {0}
Category:: WebService
Cause:: An error occurred while generating a stub implementation class or a dynamic proxy. The service implementation class does not implement a conctere service interface and thus could not be instantiated.
Action:: Ensure that specified service implementation class implements JAXRPC service interface and it's available in the classpath.

OWS-00147: dynamic invocation error: {0}
Category:: WebService
Cause:: Unexpected Error while invoking the service method.
Action:: Ensure that the DII client that invoking the serivce is configured correctly.

OWS-00148: service: {0} does not contain port: {1}
Category:: WebService
Cause:: Service Invocation failed because the <wsdl:service> element does not contain any ports.
Action:: Ensure that the <wsdl:service> element has atleast one port defined.

OWS-00149: port: {0} does not contain operation: {1}
Category:: WebService
Cause:: Service Invocation failed because service endpoint does not contain specified operation.
Action:: Ensure that DII client invoking the operation that advertised in the service descriptor i.e WSDL.

OWS-00150: property: "{0}" must be set on a Call object before it can be invoked in this configuration
Category:: WebService
Cause:: The Dynamic Invocation Interface (DII) client has not set the required property on the Call object.
Action:: For DII client, ensure that all required properties are set correctly on Call object before invoking service.

OWS-00156: call object cannot be created without a TypeRegistry
Category:: WebService
Cause:: Service Invocation failed because the InternalTypeMappingRegistry for serialization/deserialization provided to the Call object is null
Action:: System Internal Error - Contact Oracle Support Services

OWS-00157: cannot set unrecognized property: {0} on a Call object
Category:: WebService
Cause:: Client code is trying to set a property that is not specified for Call objects.
Action:: Check the name of the property that is being set. Use only properties specified for Call objects.

OWS-00158: cannot get unrecognized property: {0} on a Call object
Category:: WebService
Cause:: Client code is trying to get a property that is not specified for Call objects.
Action:: Check the name of the property that client side code is trying to access. Use only properties specified for Call objects.

OWS-00159: WSDL data missing, this operation is not available
Category:: WebService
Cause:: An unconfigured Dynamic Invocation Interface (DII) client is using the getCalls(Qname portName) method on a Service object that does not have an associated WSDL.
Action:: Either use a fully configured DII client, or use a createCall() method that explicitly specifies all required port and operation information to create a Call object instance.

OWS-00160: WSDL data missing, {0}
Category:: WebService
Cause:: An unconfigured (Dynamic Invocation Interface (DII) client uses getPort method on Service Implementation object which is not supported when WSDL information is missing
Action:: Use the configured DII client by getting the service implementation object using creteService(java.net.URL wsdlDocLoc, QName name) method on ServiceFactory object

OWS-00161: output parameters are only available after invoke() has been called
Category:: WebService
Cause:: Dynamic Invocation Interface (DII) client code is trying to get the output parameters before invoking the service
Action:: Ensure that the client code has invoked the service first before accessing the value of output parameters.

OWS-00162: cannot set parameter or return types on this Call object
Category:: WebService
Cause:: Dynamic Invocation Interface (DII) client attempted to set parameter or return types on a Call object when service operation does not require input parameter and does not return anything.
Action:: Check whether Call obect requires to set parameter or return type by calling isParameterAndReturnSpecRequired() on Call object

OWS-00163: operation style: "{0}" not supported
Category:: WebService
Cause:: Dynamic Invocation Interface (DII) Client sets the Call.OPERATION_STYLE_PROPERTY to other than 'rpc' or 'document'
Action:: Set Call.OPERATION_STYLE_PROPERTY to either 'rpc' or 'document'

OWS-00164: encoding style: "{0}" not supported
Category:: WebService
Cause:: Dynamic Invocation Interface (DII) client sets the ENCODINGSTYLE_URI_PROPERTY to an unsupported value i.e other than 'http://schemas.xmlsoap.org/soap/encoding' or null
Action:: Use either 'encoded' or 'literal' encoding style.

OWS-00165: could not find service: {0} in the specified WSDL file. The service names found were: {1}
Category:: WebService
Cause:: Service name provided by client code is not available in the specified WSDL.
Action:: Check the Service name used by the client code and ensure that correct Service name is used as per the specified WSDL.

OWS-00166: could not dispatch to method: {0} known methods are: {1}
Category:: WebService
Cause:: Operation that Dynamic Invocation Interface (DII) client code is trying to invoke does not not match with any operation provided by the service.
Action:: Make sure correct Operation name is used by the DII client code while configuring Call Object.

OWS-00167: The attachment DataHandler object cannot be null
Category:: WebService
Cause:: The attachment DataHandler object cannot be null
Action:: Make sure DataHandler attached to Call object is not null

OWS-00168: error.build.wsdl.model: {0}
Category:: WebService
Cause:: Error in the WSDL Model generation at the client side during service invocation. The useWSI property was set to true, but the WSDL does not conform to the WSI basic profile.
Action:: Ensure that the specified WSDL is compliant to Web Services Interoperability(WS-I) Basic Profile.

OWS-00169: Wrong value type {0} for property {1}. java.io.File or org.w3c.dom.Element is expected
Category:: WebService
Cause:: An unexpected value was set on a Call object. The value must be either of type java.io.File or of type org.w3c.dom.Element.
Action:: Check the type of the value being set on the Call object.

OWS-00170: serialization error: {0}
Category:: WebService
Cause:: Serializer class is missing.
Action:: Make sure the serializer class is defined and available from the classpath.

OWS-00171: deserialization error: {0}
Category:: WebService
Cause:: Deserializer failed.
Action:: Check the incoming message.

OWS-00172: encoding error: {0}
Category:: WebService
Cause:: Failed to initialize dynamic serializer/deserializer for RPC/ENC request
Action:: System Internal Error - Contact Oracle Support Services

OWS-00173: malformed array type: {0}
Category:: WebService
Cause:: The arrayType attribute is missing. The array index is less than 0 or the end index is less than the start index.
Action:: Check the incoming message. Check the incoming message.

OWS-00174: serialized array has too many elements
Category:: WebService
Cause:: At least one array element position is outside the array boundaries in the inbound message.
Action:: Check the incoming message

OWS-00175: illegal array element position: {0}
Category:: WebService
Cause:: Either the array dimension is empty and the element position is not one, or the array dimension length is not equal to the element position length.
Action:: Check the incoming message

OWS-00176: missing array position attribute
Category:: WebService
Cause:: Sparse array does not have a position attribute
Action:: Check the incoming message

OWS-00177: array element position is out of bounds: {0}
Category:: WebService
Cause:: An array position value is outside the array bounds
Action:: Check the incoming message

OWS-00178: unexpected null value during serialization or deserialization
Category:: WebService
Cause:: Serializer cannot serialize a null object for a non-nillable parameter.Deserializer cannot deserialize null to a non-nillable object.
Action:: Make sure the parameter is not null. Check the incoming message.

OWS-00179: Unexpected error while processing a SOAP Message during {0}, message={1}
Category:: WebService
Cause:
Action:

OWS-00180: unexpected reference element during deserialization; the element "{0}" is not defined as a referenceable type
Category:: WebService
Cause:: Failed to deserialize the request message. The request element uses a reference type which is not specified in the WSDL.
Action:: Correct the WSDL definition or correct the request message.

OWS-00181: unexpected element type: expected={0}, actual={1}
Category:: WebService
Cause:: Failed to deserialize the request message. The request element type does not match what is defined in the WSDL.
Action:: Correct the WSDL definition or correct the request message.

OWS-00182: unexpected element name: expected={0}, actual={1}
Category:: WebService
Cause:: Failed to deserialize the request message. The request element name does not match what is defined in the WSDL.
Action:: Correct the WSDL definition or correct the request message.

OWS-00183: unexpected array element type: expected={0}, actual={1}
Category:: WebService
Cause:: The type of an array element does not match its definition in the schema.
Action:: Verify that the type of the array element being sent matches the type defined in the schema.

OWS-00184: non-local reference (href): {0}
Category:: WebService
Cause:: The href attribute, used to reference an attachment, is not specified using the "cid" (Content-ID) protocol string.
Action:: Change the value of the href attribute, used to reference an attachment, to a string that begins with "cid:".

OWS-00185: trailing block elements must have an id attribute
Category:: WebService
Cause:: An element in the SOAP message contains a reference to another element. However no element was found with an id attribute matching the reference.
Action:: Validate the correctness of the received message.

OWS-00186: malformed array dimensions: {0}
Category:: WebService
Cause:: The dimensions of the array specified in the SOAP message cannot be translated into a valid number. The bounds of the array are invalid. For example the lower bound of the array is larger than the upper bound.
Action:: Verify that the SOAP-ENC:arrayType attribute (for SOAP 1.1) or the arraySize attribute (for SOAP 1.2) is valid.

OWS-00187: multi-dimensional array is not regular
Category:: WebService
Cause:: One level in a multi-dimensional array instance is null or contains an invalid size.
Action:: Ensure that all levels of the multi-dimensional array conatin valid values.

OWS-00188: illegal array offset: {0}
Category:: WebService
Cause:: The value specified in the "offset" attribute of an array element is invalid.
Action:: Ensure that the value specified in the offset attribute of the array element in the SOAP message is within the range of the array dimensions.

OWS-00189: array has unexpected rank: expected={0}, actual={1}, arrayType={2}
Category:: WebService
Cause:: The rank of an array does not match the rank specified in the schema.
Action:: Verify that that the soapenc:rank attribute of the array element in the schema matches with the actual dimensions of the array in the SOAPMessage.

OWS-00190: array has unexpected dimensions: expected={0}, actual={1}, arrayType={2}
Category:: WebService
Cause:: The dimensions of an array in the SOAP element do not match those of the element defined in the Schema.
Action:: Verify that the SOAP message matches the WSDL definition

OWS-00191: unexpected encoding style: expected={0}, actual={1}
Category:: WebService
Cause:: The encoding style being used in the message is invalid for the SOAP version. For example, SOAP 1.1 expects the encoding style http://schemas.xmlsoap.org/soap/encoding/ while SOAP 1.2 expects a range of values, one of which is http://www.w3.org/2003/05/soap-encoding.
Action:: Ensure that the encoding style uri of the SOAP message is valid for the version of SOAP in use. Check the SOAP 1.1 and SOAP 1.2 for acceptable values.

OWS-00192: cannot encode XML type because it was not specified
Category:: WebService
Cause:: Unable to find XML type for object.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00193: member {0} has already been defined
Category:: WebService
Cause:: While deserializing the SOAP message a duplicate member variable or setter/getter was found in the target object.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00194: incomplete object encountered while deserializing
Category:: WebService
Cause:: Failure during deserialization (XML to Java).
Action:: System Internal Error - Contact Oracle Support Services

OWS-00195: circular reference detected while serializing: {0}
Category:: WebService
Cause:: An object is referenced from another object that it references. For example A->B->A. This circular reference is not supported in RPC-Literal or Doc-Literal web services.
Action:: Remove the circular dependency or change the web service to RPC-Encoded.

OWS-00196: no attachment with cid (Content-ID) "{0}" found in message
Category:: WebService
Cause:: The cid (Content-ID) for a particular attachment that was referenced from the SOAP body was not found.
Action:: Make sure that the cid is formatted properly. Examine the cid in the soap body with the Content-Id header of the SOAP Message MIME attachment and verify that they match.

OWS-00197: multiple attachments with the same cid (Content-ID) "{0}" found in message
Category:: WebService
Cause:: Found multiple attachments with the same cid (Content-ID). This field must be unique
Action:: If the SOAP message was manually constructed, verify that all the Content-ID headers contain a unique value.

OWS-00198: missing cid (Content-ID header) for attachment
Category:: WebService
Cause:: An attachment was missing the Content-Id header.
Action:: Examine the SOAP message and verify that all Content-Id headers contain a value.

OWS-00199: non "cid:" (Content-ID) reference: {0}
Category:: WebService
Cause:: A SwaRef attachment was found with an invalid reference to a MIME attachment. MIME attachment references must begin with the string "cid:".
Action:: Verify that the attachment reference begins with "cid".

OWS-00203: serializeAsAttachment specified but no AttachmentEncoder was provided for type: "{0}"
Category:: WebService
Cause:: Missing serializer for a particular attachment type.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00204: a deserializer must be registered with a deserialization state before it will accept listeners
Category:: WebService
Cause:: A serializer class was not found during initialization of the serializer framework.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00205: cannot decode XML type "{0}"
Category:: WebService
Cause:: Unable to construct an object from an XML instance (element).
Action:: System Internal Error - Contact Oracle Support Services

OWS-00206: cannot serialize type "{0}"
Category:: WebService
Cause:: An appropriate default serializer for the specified type could not be found.
Action:: A custom serializer must be used for the indicated type. Implementing a custom serializer for a Web service is described in the Oracle Application Server Web Services Developer's Guide.

OWS-00207: null soap version not allowed.
Category:: WebService
Cause:: The SOAP message did not contain enough information to determine the version of the SOAP specification used.
Action:: Typcially the SOAP version is determined by inspecting the namespace declared on the root element (Envelope) of the SOAP message. This value should be one of http://schemas.xmlsoap.org/soap/envelope/ for SOAP 1.1 or http://www.w3.org/2003/05/soap-envelope for SOAP 1.2.

OWS-00208: cannot have enc:id and enc:ref attributes on the same element.
Category:: WebService
Cause:: The SOAP message element contains both an id and a ref attribute. Using both on the same element is illegal.
Action:: The Webservice client that created the message must be modified so that invalid SOAP messages are not created.

OWS-00209: unexpected element name: expected={0}, actual={1}
Category:: WebService
Cause:: The deserializer encountered an unexpected element name when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that the SOAP messages it creates conform to the messages described in this Webservice's WSDL.

OWS-00210: unexpected element type: expected={0}, actual={1}
Category:: WebService
Cause:: The deserializer encountered an unexpected element type when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that the SOAP messages it creates conform to the messages described in this Webservice's WSDL.

OWS-00211: unexpected null
Category:: WebService
Cause:: The (de)serializer encountered an unexpected null element/object when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that the SOAP messages it creates conform to the messages described in this Webservice's WSDL.

OWS-00212: unknown prefix in QName literal: {0}
Category:: WebService
Cause:: The deserializer cannot figure out the Namespace URI for the given prefix when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that invalid SOAP messages are not created.

OWS-00213: invalid XSD date: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD date when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD dates are not created.

OWS-00214: invalid XSD boolean value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD boolean when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD boolean are not created.

OWS-00215: attachment location not found on element
Category:: WebService
Cause:: The deserializer cannot determine the attachment location on an element with binary type.
Action:: The Webservice client that created the message must be modified so that SOAP messages with attachments will correctly reference the attachments.

OWS-00216: attachment with id {0} not found in message
Category:: WebService
Cause:: The deserializer cannot find the attachment from the specified location on an element with binary type.
Action:: The Webservice client that created the message must be modified so that SOAP messages with attachments will correctly reference the attachments.

OWS-00217: invalid XSD positiveInteger value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD positiveInteger when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD positiveInteger are not created.

OWS-00218: invalid XSD nonNegativeInteger value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD nonNegativeInteger when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD nonNegativeInteger are not created.

OWS-00219: invalid XSD negativeInteger value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD negativeInteger when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD negativeInteger are not created.

OWS-00220: invalid XSD nonPositiveInteger value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD nonPositiveInteger when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD nonPositiveInteger are not created.

OWS-00222: invalid XSD unsignedLong value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD unsignedLong when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedLong are not created.

OWS-00223: invalid XSD unsignedInt value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD unsignedInt when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedInt are not created.

OWS-00224: invalid XSD unsignedShort value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD unsignedShort when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedShort are not created.

OWS-00225: invalid XSD unsignedByte value: {0}
Category:: WebService
Cause:: The deserializer encountered an invalid XSD unsignedByte when processing the SOAP message.
Action:: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedByte are not created.

OWS-00227: error in initialization of standard type mapping: {0}
Category:: WebService
Cause:: Internal error initializing the standard type mapping.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00228: {0} : is not a supported (de)serialization mechanism
Category:: WebService
Cause:: The (de)serializer factory does not support the reported XML processing mechanism type.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00229: type mapping registration failed: {0}
Category:: WebService
Cause:: An unexpected error occurred during registration of a Java to XML mapping. Check the nested error for the real cause.
Action:: Look at the nested error to determine what action to take.

OWS-00230: type mapping retrieval failed: {0}
Category:: WebService
Cause:: An unexpected error occurred during retrieval of a Java to XML mapping. Check the nested error for the real cause.
Action:: Look at the nested error to determine what action to take.

OWS-00231: type mapping does not support the specified encoding style: {0}
Category:: WebService
Cause:: The system does not support the specified schema type and encoding.
Action:: Change the encodingStyle defined in the SOAP binding in the WSDL to a supported value.

OWS-00232: there is no type mapping for the specified encoding style: {0}
Category:: WebService
Cause:: The system does not support the specified encoding.
Action:: Change the encodingStyle defined in the SOAP binding in the WSDL to a supported value.

OWS-00233: no serializer is registered for ({0}, {1})
Category:: WebService
Cause:: The system could not find a serializer that can convert the Java object to XML.
Action:: Create a custom type mapping and serializer that can covert the Java object to XML.

OWS-00234: no deserializer is registered for (java type: {0}, schema type: {1})
Category:: WebService
Cause:: The system could not find a deserializer that can convert the XML to a Java object.
Action:: Create a custom type mapping and serializer that can covert the XML to a Java object.

OWS-00235: no deserializer is registered for schema type: {0}
Category:: WebService
Cause:: The system could not find a deserializer that can convert the XML to a Java object.
Action:: Create a custom type mapping and serializer that can covert the XML to a Java object.

OWS-00236: no deserializer is registered for java type: {0}
Category:: WebService
Cause:: The system could not find a deserializer that can convert the XML to a Java object.
Action:: Create a custom type mapping and serializer that can covert the XML to a Java object.

OWS-00237: dynamic resolution failed to find a serializer for java type:{0}, xml type {1}
Category:: WebService
Cause:: An entry in a list or collection is a type that is not supported by the system.
Action:: Change the instance of the entry to a supported Java type.

OWS-00238: dynamic resolution failed to find a serializer for java type: {0}, xmlType: {1}
Category:: WebService
Cause:: An entry in a list or collection is a type that is not supported by the system.
Action:: Change the instance of the entry to a supported Java type.

OWS-00241: Map entry key cannot be of java type:"{0}", xml type "{1}"
Category:: WebService
Cause:: The key for a map entry has a type mapping for an object that the system does not support.
Action:: Change the signature of the Java class to a supported Java type or change the instance of the key to a supported type.

OWS-00242: Map entry value cannot be of Java type:"{0}", XML type was "{1}"
Category:: WebService
Cause:: The value for a map entry has a type mapping for an object that the system does not support.
Action:: Change the signature of the Java class to a supported Java type or change the instance of the value to a supported type.

OWS-00243: Item in array cannot be of java type:"{0}"
Category:: WebService
Cause:: An item in an array is a type that is not supported by the system.
Action:: Change the signature of the Java class to a supported Java type or change the instance of the value to a supported type.

OWS-00245: unexpected null value for literal data
Category:: WebService
Cause:: The element defined in the schema has a nillable attribute set to false but no value was found in the message.
Action:: Change the client to supply a value for the literal type, or change the schema to accept nillable types.

OWS-00246: unexpected element name: expected={0}, actual={1}
Category:: WebService
Cause:: A message contains an element that the system does not expect.
Action:: Change the client to send messages corresponding to the schema, or change the schema to correspond to the messages.

OWS-00247: expected element is missing: {0}
Category:: WebService
Cause:: The message does not contain an element that is defind as required in the schema.
Action:: Change the schema to make the element optional, or change the client so that the message will include the required element.

OWS-00248: expected simple content, found element name: {0}
Category:: WebService
Cause:: The system was expecting a simple content in the message but found an element instead.
Action:: Change the client to send messages corresponding to the schema, or change the schema to correspond to the messages.

OWS-00249: object not initialized before use
Category:: WebService
Cause:: A serializer was not initialized before calling a method that requires initialization.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00250: {0} is not an array type
Category:: WebService
Cause:: The system found a Java object that is not an array when an array is expected.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00251: expected {0} parameter(s) but received: {1}. Expected parameters: {3}, received parameters:{4}
Category:: WebService
Cause:: The number of parameters in the request SOAP message is incorrect.
Action:: Confirm that the client is based on the correct version of the WSDL definition.

OWS-00252: illegal deserialization state: no deserializer is available for the current element
Category:: WebService
Cause:: There is no deserializer registered for the element.
Action:: A custom serializer must be used for the indicated type. Implementing a custom serializer for a Web service is described in the Oracle Application Server Web Services Developer's Guide.

OWS-00253: Invalid base64 data
Category:: WebService
Cause:: The SOAP request content being processed by the XSDBase64BinaryEncoder is not Base64 encoded.
Action:: Confirm that the client is based on the correct, current version of the WSDL document.

OWS-00254: generator error: {0}
Category:: WebService
Cause:: An unexpected exception occurred during a generation operation.
Action:: Contact Oracle Support Services.

OWS-00255: can''t write file: {0}
Category:: WebService
Cause:: A generated file could not be written to disk. The most likely causes include insufficient disk space or permissions.
Action:: Free some disk space or ensure that the process in which the generator is invoked is run as a user with sufficient permissions.

OWS-00256: can''t create directory: {0}
Category:: WebService
Cause:: The directory for writing a generated file could not be created. The most likely causes include insufficient disk space or permissions.
Action:: Free some disk space or ensure that the process in which the generator is invoked is run as a user with sufficient permissions.

OWS-00257: unsupported type encountered: '{'{1}'}'{0}
Category:: WebService
Cause:: Serialization is not supported for this XML type.
Action:: A custom serializer must be used for the indicated type. Implementing a custom serializer for a Web service is described in the Oracle Application Server Web Services Developer's Guide.

OWS-00258: no Java type for XML type: {0}
Category:: WebService
Cause:: Unable to determine the corresponding Java type for a structured XML type when generating a serializer.
Action:: Ensure that a Java type is associated with the structured XML type and that the custom serializer mapping is correct.

OWS-00259: unsupported encoding encountered: {0}
Category:: WebService
Cause:: The encoding URI of custom serializer mapping does not match that of either SOAP 1.1 or SOAP 1.2.
Action:: Correct the URI encoding of the custom serializer mapping.

OWS-00260: tie class generation error: {0}
Category:: WebService
Cause:: When generating the tie class for a document literal operation, either more than one non-embedded parameter was found, or there were both embedded and non-embedded parameter.
Action:: This sanity check should not have failed. Verify that the document literal operation is correct in the WSDL.

OWS-00262: There is no management configuration for port {0} in the supplied proprietary deployment descriptor. Ensure that the port name is correct
Category:: WebService
Cause:: There is no management configuration information for the port in the supplied management configuration file.
Action:: Verify that the port name is correct and the management configuration file is complete.

OWS-00263: Could not find the Java class {0} for constructor analysis.
Category:: WebService
Cause:: Could not find the Java class for constructor analysis when generating its serializer.
Action:: Check the Java class name and the classpath where the Java class is loaded.

OWS-00264: Current SOAP Version is null. Check port to make sure SOAP version is set.
Category:: WebService
Cause:: Could not determine the SOAP version when generating serializer.
Action:: Verify that the SOAP version is set in the WSDL.

OWS-00266: When using JMS transport, either all operations must be one-way, or the replyToConnectionFactoryLocation and replyToQueueLocation must be specified.
Category:: WebService
Cause:: When using JMS transport for any two-way operation, the replyToConnectionFactoryLocation and replyToQueueLocation parameters must be specified with the jsmAssemble command.
Action:: Re-run the jmsAssemble command with replyToConnectionFactoryLocation and replyToQueueLocation parameters.

OWS-00267: cannot dispatch operation with more that one body block: {0}
Category:: WebService
Cause:: Cannot generate tie class for operations with more than one body block.
Action:: Verify that the offending operation has no more than one body block.

OWS-00268: cannot dispatch operation - either operation names are non-unique, or SOAPAction strings are non-unique: {0}
Category:: WebService
Cause:: Cannot generate tie class for operation with non-unique operation name and non-unique SOAPAction.
Action:: Verify that both the operation name and SOAPAction are unique in the WSDL.

OWS-00269: no encoder for type "{0}" and Java type "{1}"
Category:: WebService
Cause:: Unable to find an encoder for a type and its corresponding Java type when generating serializer.
Action:: Check whether the type is valid and supported.

OWS-00270: Invalid type in xsd:list type "{0}" and Java type "{1}"
Category:: WebService
Cause:: Unable to find an encoder for the list item type and its corresponding Java type when generating serializer.
Action:: Check whether the list item XML type is valid and supported.

OWS-00271: handler error: {0}
Category:: WebService
Cause:: A handler error occurred, check the nested error for the real cause.
Action:: Look at the nested error to determine what action to take.

OWS-00272: A HandlerChain can only contain Handler instances: {0}
Category:: WebService
Cause:: A non-handler instance was found in the handler chain.
Action:: Remove the offending instance,

OWS-00274: cannot create XSLT transformer for the WSDL
Category:: WebService
Cause:: Failed to create a XSLT Transformer object for presentation of WSDL.
Action:: Check whether the web service endpoint is valid and the service is properly deployed.

OWS-00275: WSDL transformation failed
Category:: WebService
Cause:: XSLT Transformation failed when presenting WSDL.
Action:: Check whether the web service endpoint is valid and the service is properly deployed.

OWS-00276: model error: {0}
Category:: WebService
Cause:: A nested model or modeler exception occurred, most likely caused by an invalid WSDL.
Action:: Verify that the WSDL is a valid one.

OWS-00277: unsupported XML Schema feature ({0})
Category:: WebService
Cause:: An unsupported XML Schema feature was encountered during processing of WSDL schema.
Action:: Remove the unsupported XML Schema feature from WSDL schema.

OWS-00278: unsupported type ({0}): {2}:{1}
Category:: WebService
Cause:: An unsupported XML Schema type was encountered during processing of a WSDL schema element.
Action:: Remove the unsupported type or change it to an equivalent supported type.

OWS-00279: unsupported type ({0}): {1}, caused by: {3}
Category:: WebService
Cause:: An unsupported XML Schema type was encountered during processing of a WSDL schema element. Error details are provided.
Action:: Look at the error details for possible action to handle the unsupported type.

OWS-00280: unsupported anonymous type ({0}), caused by: {1}
Category:: WebService
Cause:: An unsupported XML Schema type was encountered during processing of an anonymous WSDL schema element. Error details are provided.
Action:: Look at the error details for possible action to handle the unsupported type.

OWS-00281: invalid literal "{0}" in enumeration "{1}" (namespace: {2})
Category:: WebService
Cause:: An invalid literal value of an enumeration was encountered when processing a WSDL schema.
Action:: Correct the offending literal value in the enumeration.

OWS-00282: uniqueness constraint violation: {0} "{1}" already exists.
Category:: WebService
Cause:: A component with the specified name occurs multiple times
Action:: Check the validity of the WSDL or Java code for duplicate elements

OWS-00283: The value type {0} can not be generated because two members result in the same name of {1}. A jaxrpc mapping file must be specified to resolve this naming conflict.
Category:: WebService
Cause:: There is a naming conflict - two members have the same name
Action:: Use a JAX-RPC mapping file.

OWS-00285: parent of type "{0}" already set to "{1}", new value = "{2}"
Category:: WebService
Cause:: The specified type is duplicated within more than one parent type.
Action:: Rewrite the type hierarchy, so that this type only occurs on one parent.

OWS-00286: parent of fault "{0}" already set to "{1}", new value = "{2}"
Category:: WebService
Cause:: The specified fault is duplicated as a sub-type of more than one parent.
Action:: Ensure that the fault only occurs within a single parent.

OWS-00287: LiteralArrayWrapper element member already set.
Category:: WebService
Cause:: This element cannot be modeled as a LiteralArrayWrapper because it has more than one member
Action:: None

OWS-00288: LiteralArrayWrapper cannot have a parent type
Category:: WebService
Cause:: This element cannot be modeled as a LiteralArrayWrapper because it has a parent type
Action:: None

OWS-00289: LiteralArrayWrapper cannot have subtypes
Category:: WebService
Cause:: This element cannot be modeled as a LiteralArrayWrapper because it has a subtype
Action:: None

OWS-00290: LiteralArrayWrapper cannot have a content member
Category:: WebService
Cause:: This element cannot be modeled as a LiteralArrayWrapper because it has a content member
Action:: None

OWS-00293: class {0} not found.
Category:: WebService
Cause:: The specified Java class could not be loaded.
Action:: The class must exist in the classpath when strictJAXRPCValidation is turned on.

OWS-00295: unexpected type: {0}
Category:: WebService
Cause:: An unexpected type was found during the processing of your action. In the case of top-down design the WSDL contains an unsupported or invalid type. In the case of bottom-up design, the particular class file is currently not supported.
Action:: Top-down design pattern: Correct any problems within the WSDL file. If the WSDL is valid, then it contains types that are currently not supported. Bottom-up design pattern: Correct any type issues within the Java class. Otherwise, the class contains types that are currently not supported. You may want to consider using a different type.

OWS-00296: The following type is invalid because it implements java.rmi.Remote: {0}
Category:: WebService
Cause:: The serializable implementation class inappropriately implements java.rmi.Remote. This is not supported.
Action:: Change the implementation class to not implement java.rmi.Remote.

OWS-00297: class {0} does not have a public accessible empty constructor
Category:: WebService
Cause:: The serializable implementation class does not provide a public accessible no-arg constructor.
Action:: Provide a public no-arg constructor or provide a custom seriallizer.

OWS-00299: class "{0}" cannot have a JavaBean property "{1}" and a public member of the same name.
Category:: WebService
Cause:: The implementation class cannot contain public members with the same name as JavaBean properties.
Action:: Consider making the public member private or protected or renaming the property or JavaBean property.

OWS-00300: nested inner classes are not supported: {0}
Category:: WebService
Cause:: The implementation class contains a nested inner class, which is not supported.
Action:: Consider refactoring the implementation class to remove the nested inner class. See the Oracle Application Server Web Services Developer's Guide.

OWS-00301: Duplicate type name "{0}" for Java type "{1}" found. To remove this error do not specify a single typeNamespace for all value types or specify a mapping file. This error could also be caused when a type name has been used more than once.
Category:: WebService
Cause:: The same type name has been used for multiple Java types. Probably related to inner classes. A possible explanation is the erroneous use of a given type name multiple times.
Action:: Use separate namespaces for the value types or use a mapping file. See the Oracle Application Server Web Services Developer's Guide.

OWS-00302: Type "{0}" is used as a "{1}" and a "{2}"
Category:: WebService
Cause:: The same RMI Modeler type instance is used for two different XML types.
Action:: Correct the XML type or the XML type hierarchy such that there is one Modeler per XML type, or have one type subclass the other type.

OWS-00303: Type "{0}" implements more than one interface: "{1}", "{2}" ...
Category:: WebService
Cause:: The implementation class may implement only a single interface (SEI).
Action:: Consider refactoring the implementation class to implement a single interface.

OWS-00304: Type {0} references an invalid type {1}, which is invalid for the following reason: {2}
Category:: WebService
Cause:: The indicated type has a reference to an invalid type.
Action:: Consider modifying the implementation class to not reference the inappropriate type.

OWS-00305: Ignoring target namespace for schema: "{0}", WSDL target namespace is used for the value types in the same package as Service Endpoint: "{1}"
Category:: WebService
Cause:: The schema namespace is ignored and the WSDL target namespace will be used instead. This is because the namespace of the schema is different from the target namespace of the WSDL and the value types are in the same package as the Service Endpoint Interface (SEI).
Action:

OWS-00306: The constructor for {0} has {1} arguments of type {2}; This ambiguity may result in unexpected behavior. Use a mapping file to guarantee correctness.
Category:: WebService
Cause:: Multiple arguments of the same type introduce ambiguity that is difficult to resolve. This may cause unexpected results.
Action:: Consider using a JAX-RPC mapping file to eliminate the ambiguity.

OWS-00307: Service-specific exception {0} is not allowed to extend {1}.
Category:: WebService
Cause:: Runtime exceptions other than SOAPFaultException are not allowed.
Action:: Consider changing the exception to not be a runtime exception or make it a SOAPFaultException.

OWS-00308: Service-specific exception {0} is not allowed to implement {1}.
Category:: WebService
Cause:: Service exceptions must not implement the java.rmi.Remote interface.
Action:: Consider changing the exception to not implement Remote.

OWS-00314: invalid operation: {0}
Category:: WebService
Cause:: Invalid WSDL operation due to incorrect parameter order.
Action:: Correct the parameter order of the specified operation.

OWS-00315: invalid state while modeling operation: {0}
Category:: WebService
Cause:: System Internal Error
Action:: Contact Oracle Support Services

OWS-00316: result is "inout" parameter in operation: {0}
Category:: WebService
Cause:: In/out parameters are not allowed.
Action:: Consider changing the implementation to return a value.

OWS-00317: "{0}" specified in the parameterOrder attribute of message "{1}" is not a valid part of the message.
Category:: WebService
Cause:: The specified parameter(s) in parameterOrder of portType operation is not a valid part of the message.
Action:: Verify and correct the part name parameter specified in the WSDL portType: ensure that the operation parameterOrder is properly associated and used in the input and output message.

OWS-00318: one or more part names were omitted in the parameterOrder attribute of operation "{0}"
Category:: WebService
Cause:: A message part name was not specified in the WSDL portType operation parameterOrder.
Action:: Verify that input and output message part name are properly specified in the WSDL portType operation parameterOrder.

OWS-00319: parameter "{0}" of operation "{1}" appears with different types in the input and output messages
Category:: WebService
Cause:: The parameter used in an operation appears with different types in the input and output message.
Action:: Verify the type of the input and output message specified in the WSDL portType operation.

OWS-00320: missing header message definition for "{1}", referenced by the binding operation "{0}"
Category:: WebService
Cause:: The soap header message defined in the binding operation is not specified in the WSDL message definition.
Action:: Verify the soap header message defined in the binding operation. Ensure that it is properly specified in the WSDL message definition.

OWS-00321: missing operation "{0}" in port type, referenced by binding "{1}"
Category:: WebService
Cause:: The operation specified in binding does not appear in the corresponding port type.
Action:: Verify the binding operation. Ensure that it is specified in the corresponding port type in the WSDL.

OWS-00322: input message of binding operation "{0}" does not have a SOAP body extension
Category:: WebService
Cause:: The input message of the binding operation does not have a SOAP body extension.
Action:: Verify that the SOAP body extension 'soap:body' is properly specified in the input message of the binding operation in the WSDL.

OWS-00323: output message of binding operation "{0}" does not have a SOAP body extension
Category:: WebService
Cause:: The output message of a binding operation does not have a SOAP body extension.
Action:: Verify that the SOAP body extension 'soap:body' is properly specified in the output message of the binding operation in the WSDL.

OWS-00324: input message of binding operation "{0}" must specify a value for the "namespace" attribute
Category:: WebService
Cause:: The soap request body of the input message of a binding operation must specify a value for the namespace attribute.
Action:: Verify that the namespace attribute is properly specified in the soap request body of the input message of this binding operation in the WSDL.

OWS-00325: output message of binding operation "{0}" must specify a value for the "namespace" attribute
Category:: WebService
Cause:: The soap request body of the output message of a binding operation must specify a value for the namespace attribute.
Action:: Verify that the namespace attribute is properly specified in the soap request body of the output message of this binding operation in the WSDL.

OWS-00326: fault "{0}" in operation "{1}" matches more than one fault in the corresponding port type operation
Category:: WebService
Cause:: The fault in a binding operation matches more than one fault in the corresponding port type operation.
Action:: Verify the exact correspondence between the fault name in the binding operation and in the port type operation of the WSDL.

OWS-00327: fault "{0}" in operation "{1}" does not match any fault in the corresponding port type operation
Category:: WebService
Cause:: The fault in a binding operation does not match any fault in the corresponding port type operation.
Action:: Verify the the correspondence between the fault name in the binding operation and in the port type operation of the WSDL.

OWS-00328: fault "{0}" in operation "{1}" does not have a SOAP fault extension
Category:: WebService
Cause:: The fault in a binding operation does not have a SOAP fault extension.
Action:: Verify that the SOAP fault extension 'soap:fault' is properly specified in this fault of the binding operation.

OWS-00329: fault "{0}" refers to message "{1}", but the message has no parts
Category:: WebService
Cause:: The fault refers to a message in definitions, but the message has no parts.
Action:: Verify and ensure the fault message with properly specified part name in the WSDL.

OWS-00330: fault "{0}" refers to message "{1}", but the message has more than one parts
Category:: WebService
Cause:: The fault refers to a message in definitions, but the message has more than one parts.
Action:: Verify and correct the fault message with properly and exactly specified part name in the WSDL.

OWS-00331: in message "{0}", part "{1}" must specify a "type" attribute
Category:: WebService
Cause:: In this WSDL, there is part must specify a type attribute in message.
Action:: Verify the message in WSDL to ensure some part which also need a type definitions.

OWS-00332: in message "{0}", part "{1}" must specify an "element" attribute
Category:: WebService
Cause:: In this WSDL, there is part in message must specify an element attribute.
Action:: Verify the message in WSDL to ensure some part which also need an element definitions.

OWS-00334: the following naming conflicts occurred: {0}
Category:: WebService
Cause:: There are naming conflicts occurred in WSDL.
Action:: Verify the naming in WSDL is properly and correctly without conflict.

OWS-00335: Unsupported DIME layout: {0}
Category:: WebService
Cause:: The DIME message layout specified in the operation is not supported.
Action:: Verify and check the DIME layout specified. The supported layout are: closed-layout and open-layout.

OWS-00336: binding "{0}" uses both streaming attachments and mime-multipart
Category:: WebService
Cause:: There is binding which uses both streaming attachments and mime-multipart in WSDL.
Action:: Verify and correct the WSDL binding to ensure not both streaming attachments and mime-multipart is used.

OWS-00337: binding "{0}" uses both streaming attachments and DIME
Category:: WebService
Cause:: There is binding which uses both streaming attachments and DIME message in WSDL.
Action:: Verify and correct the WSDL binding to enusre not both streaming attachments and DIME is used.

OWS-00338: <portType> definition is not found in the WSDL
Category:: WebService
Cause:: There is no service and portType definition found in the WSDL.
Action:: Verify and check the WSDL. Either service or portType has to be defined and specified.

OWS-00339: IO error in processing schemas: {0}
Category:: WebService
Cause:
Action:

OWS-00340: The value of service-interface {0} MUST be package qualified. It is changed to {1}.
Category:: WebService
Cause:
Action:

OWS-00341: unrecognized type encountered: {0}
Category:: WebService
Cause:
Action:

OWS-00342: exception occurred while processing type {0}, {1}
Category:: WebService
Cause:
Action:

OWS-00343: Service "{0}" does not contain any usable ports
Category:: WebService
Cause:: There is no port in the current WSDL that is suitable for JAXRPC based proxy generation.
Action:: Correct the WSDL, based on the other error or warning provided, so that there is one port in the current WSDL suitable for JAXRPC based proxy generation.

OWS-00344: Port "{0}" does not contain any usable operations
Category:: WebService
Cause:
Action:

OWS-00345: ignoring port "{0}": because it references "{1}" that does not contain a SOAP Binding. Only soap:binding is supported.
Category:: WebService
Cause:
Action:

OWS-00346: ignoring port "{0}": no SOAP address specified
Category:: WebService
Cause:: The "service/port" element is missing a required child element for SOAP binding: "soap:address".
Action:: Add the missing element in the original WSDL or using a local copy if you do not own the service endpoint.

OWS-00347: ignoring operation "{0}": not request-response or one-way
Category:: WebService
Cause:
Action:

OWS-00348: ignoring RPC-style operation "{0}": parameters are not encoded
Category:: WebService
Cause:
Action:

OWS-00349: ignoring operation "{0}": message part does not refer to a schema element declaration or refers to a schema type declaration without specifiying the name attribute.
Category:: WebService
Cause:
Action:

OWS-00350: ignoring header "{0}" of binding operation "{1}". This header must be mapped to a parameter using a jaxrpc mapping file or the information in the header will be ignored at runtime.
Category:: WebService
Cause:
Action:

OWS-00351: ignoring header "{0}" of binding operation "{1}": not literal
Category:: WebService
Cause:
Action:

OWS-00352: ignoring header "{0}" of binding operation "{1}": not SOAP-encoded
Category:: WebService
Cause:
Action:

OWS-00353: ignoring header "{0}" of operation "{1}": its type is not constant across all operations in this port
Category:: WebService
Cause:
Action:

OWS-00354: ignoring MIME part "{0}" of operation "{1}": either the part was not found in the specified message or the "mimePartToParameter" flag was set to false.
Category:: WebService
Cause:
Action:

OWS-00355: value type package prefix is ignored for the types defined in the schema that has same target namespace as the target namespace of WSDL: "{0}"
Category:: WebService
Cause:
Action:

OWS-00356: binding "{0}" is ignored because it has an invalid attribute: transport="{1}"
Category:: WebService
Cause:: The value of the transport attribute on the soap:binding element is not recognized. The SOAP1.1 value is "http://schemas.xmlsoap.org/soap/http".
Action:: Correct the value of the transport attribute in the original WSDL or use a local copy if you do not own the service endpoint.

OWS-00357: ignoring document-style operation "{0}": parameters are not literal
Category:: WebService
Cause:: The value for the "use" attribute on document-style binding is invalid. the only value supported is "literal".
Action:: Correct the original WSDL or use a local copy if you do not own the service endpoint.

OWS-00358: ignoring operation "{0}": input message with multiparts is not WS-I compliant and is not currently supported
Category:: WebService
Cause:: The wsdl:message referenced by the portType/operation/input element contains more than one part and doesnt comply with WS-I BP 1.1.
Action:: If you have control over the WSDL, changes the message style for bare to wrapped, so that the WSDL comply with WS-I profile. Otherwise, use the SAAJ APIs to invoke the service without to use JAXRPC generated proxy.

OWS-00359: ignoring operation "{0}": output message with multiparts is not WS-I compliant and is not currently supported
Category:: WebService
Cause:: The wsdl:message referenced by the portType/operation/output element contains more than one part and doesnt comply with WS-I BP 1.1.
Action:: If you have control over the WSDL, changes the message style for bare to wrapped, so that the WSDL comply with WS-I profile. Otherwise, use the SAAJ APIs to invoke the service without to use JAXRPC generated proxy.

OWS-00360: The WSDL used has operations with literal and encoded use. -f:searchschema is not supported for this scenario.
Category:: WebService
Cause:: The WSDL has soapbinding subelements with use="literal" as well as use="encoded". Searching of Schema is not supported for this scenario.
Action:: Modify the WSDL to have only use="literal" or use="encoded"

OWS-00361: ignoring fault "{0}" of operation "{1}", part name "{2}" is not unique
Category:: WebService
Cause:: The WSDL uses the fault partname more than once.
Action:: Update WSDL to specify unique fault part name.

OWS-00362: Notification operation "{0}" in binding "{1}" is not supported.
Category:: WebService
Cause:: Notification operations are not supported.
Action:: Use a WSDL with no notification operations.

OWS-00363: Non conforming WSI WSDL used for wsdl:import
Category:: WebService
Cause:: WSDL import element doesnt comply with WS-I
Action:: Update the WSDL so that the imports precede all other top level elements in the WSDL.

OWS-00364: Non conforming WSI WSDL used for wsdl:types
Category:: WebService
Cause:: WSDL types element doesnt comply with WS-I
Action:: Update the WSDL so that the wsdl:types elements appear immediately after the wsdl:imports or if no imports are present wsdl:types should be the first top level element.

OWS-00365: parts "{0}" not found in the message "{1}", wrong WSDL
Category:: WebService
Cause:: The part defined in the input soap body of the binding is not specified in the input message of the operation in the port type. The part defined in the output soap body of the binding is not specified in the output message of the operation in the port type.
Action:: Make sure all the parts that are defined in the input soap body of the binding are defined in the input message of the corresponding operation of the port type. make sure all the parts that are defined in the output soap body of the binding are defined in the output message of the corresponding operation of the port type.

OWS-00366: Custom mappings for rpc-encoded web service is not supported (operation = "{0}").
Category:: WebService
Cause:: the WSDL uses custom mappings and rpc encoded webservices.
Action:: If WSDL has rpc encoded bindings do not specify custom serializers. "schema" argument to Web Services Assembler along with a message format of rpc encoded is not allowed. <type-mapping> in the oracle-webservices.xml is also not allowed with rpc encoded webservices.

OWS-00367: a class by name : "{0}" is already available in the classpath
Category:: WebService
Cause:
Action:

OWS-00368: failed to make an unique serializer class : "{0}" , the error :"{1}"
Category:: WebService
Cause:
Action:

OWS-00369: failed to find accessor method "{0}" in Java type "{1}"
Category:: WebService
Cause:
Action:

OWS-00370: model is missing
Category:: WebService
Cause:: The system is missing a model.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00371: Ignoring Unique Schema Constraint
Category:: WebService
Cause:: The schema used by the WSDL has a unique constraint.
Action:: Remove unique constraint

OWS-00372: The key element has not been implemented
Category:: WebService
Cause:: The WSDL uses the unsupported "key" schema element.
Action:: Modify the schema to remove the key element

OWS-00373: Model group definition has not been implemented
Category:: WebService
Cause:: The WSDL uses a schema with a model group definition
Action:: Modify the schema to remove the model group definition

OWS-00374: Substitution Group Attribute has not been implemented
Category:: WebService
Cause:: The WSDL references a schema that uses the substitutionGroup facility.
Action:: Modify the schema to remove the substitutionGroup element

OWS-00375: Block attribute has not been implemented
Category:: WebService
Cause:: The WSDL refers to a schema that uses an unsupported block attribute.
Action:: Update your schema to set "" or #all as values for the block attribute. All other values are unsupported.

OWS-00377: Base attribute must be specified in restriction tag.
Category:: WebService
Cause:: The base attribute is not specified in the restriction tag.
Action:: Specify a base type from which the complex type is to be derived by restriction.

OWS-00378: Enumeration {0} is not supported
Category:: WebService
Cause:: The enumeration is not supported.
Action:: Modify the schema to remove this enumeraton.

OWS-00379: Attribute restriction is not supported
Category:: WebService
Cause:: The base type has an attribute element with the use="prohibited".
Action:: Remove the use="prohibited" attribute on the base type.

OWS-00380: Group Schema Element has not been implemented
Category:: WebService
Cause:: The "group" schema element is not supported
Action:: Modify the schema to remove the group element

OWS-00381: Unsupported Schema Element
Category:: WebService
Cause:: Facets are not supported in the extension and restriction elements.
Action:: Remove facets (elements like xsd:pattern, xsd:minInclusive etc which restrict values of an element) from your schema.

OWS-00382: Invalid value ({0}) for "minOccurs" attribute of element - {1}. Setting value to 0.
Category:: WebService
Cause:: Invalid "minOccurs" attribute value. Setting value to 0.
Action:: Set minOccurs to 0 if the assoicating element is optional. Otherwise, set the value to 1 or more.

OWS-00383: The "maxOccurs" attribute of the {0} element has an unsupported value of {1}. Currently only boundless arrays are supported. maxOccurs must be 0,1 or unbounded. Setting to default value of "unbounded".
Category:: WebService
Cause:: Invalid or unsupported "maxOccurs" attribute value. Setting value to 0.
Action:: Set this value to a positive integer or unbounded to indicate there is no maximum number of occurrences.

OWS-00384: Value ({0}) for "final" attribute of element -{1} is currently not supported. This attribute is ignored.
Category:: WebService
Cause:: Unsupported final attribute value. Ignore the attribute.
Action:: Set this value to "#all" or ""

OWS-00386: sender error: {0}
Category:: WebService
Cause:: Invalid configuration in oracle-webservices.xml or wsmgmt.xml.
Action:: Verify the configuration setting in oracle-webservices.xml and/or wsmgmt.xml.

OWS-00387: missing body information
Category:: WebService
Cause:: SOAP Body is missing in the request. The SOAP message was not sent.
Action:: Verify request.getBody() returns a SOAP body instance.

OWS-00388: illegal value of "mustUnderstand" attribute: "{0}"
Category:: WebService
Cause:: Response contains illegal value of "mustUnderstand" attribute.
Action:: Verify the response SOAP message. Attribute "mustunderstand" must have a value of "0", "1", "true", or "false".

OWS-00389: unrecognized operation (code: {0})
Category:: WebService
Cause:: The SOAP message is invalid. It cannot be resolved to an operation's request or response.
Action:: Regenerate the stub using either Jdeveloper or the Web Service Assembler tool.

OWS-00390: unrecognized fault block
Category:: WebService
Cause:: The response fault is invalid.
Action:: Verify the content of the fault response.

OWS-00391: received empty response
Category:: WebService
Cause:: No SOAP Message is returned from the server.
Action:: Verify the corresponding WSDL operation is not oneWay.

OWS-00392: stub was not initialized
Category:: WebService
Cause:: The initialize() method of the stub was not invoked.
Action:: Regenerate the stub using either JDeveloper or the Web Service Assembler tool. If problem persists, contact Oracle Support Services.

OWS-00395: XML reader internal error: illegal state ({0})
Category:: WebService
Cause:: XMLReader encounters an XML element that cannot be deserialized.
Action:: Validate the XML document.

OWS-00396: XML reader error: unexpected character content: "{0}"
Category:: WebService
Cause:: XMLReader encounters an element with an unexcpected character content.
Action:: Validate the XML document.

OWS-00397: XML reader error: {0}
Category:: WebService
Cause:: XMLReader cannot close the reading stream.
Action:: Check network connection and file system connection.

OWS-00398: XML parsing error: {0}
Category:: WebService
Cause:: XMLReader cannot read the next element.
Action:: Validate the XML document.

OWS-00400: XML writer error: no prefix for URI: "{0}"
Category:: WebService
Cause:: No prefix is specified for the URI.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00401: XML writer error: {0}
Category:: WebService
Cause:: XML Writer encounters an IOException.
Action:: Check network connection and file system connection.

OWS-00403: unexpected XML reader state. expected: {0} but found: {1}
Category:: WebService
Cause:: The XML document does not have the expected start or end of an element.
Action:: Check if any required element is missing or there are more elements where an end tag was expected.

OWS-00405: unrecognized operation: {0}
Category:: WebService
Cause:: The soap operation is not valid.
Action:: Check the operation name in the message and correct it.

OWS-00406: cannot dispatch ambiguous operation: {0}
Category:: WebService
Cause:: The specified operation is overloaded.
Action:: Remove the overloading by renaming one of the conflicting operations.

OWS-00407: unexpected header block: "{0}"
Category:: WebService
Cause:: The QName of the header block is not correct.
Action:: Correct the header block by verifying its namespace.

OWS-00408: invalid SOAP envelope: body is empty
Category:: WebService
Cause:: The body of the soap message is empty.
Action:: Provide the write content in the body element of the soap message.

OWS-00409: invalid SOAP envelope: body is missing
Category:: WebService
Cause:: The body element is either missing or its namespace is wrong.
Action:: Add the body if missing or correct the namespace of the body element.

OWS-00410: env:Body must be present in a SOAP 1.2 envelope
Category:: WebService
Cause:: The body element is missing from the message. SOAP 1.2 requires that the env:Body element must be present.
Action:: Add the soap body in the message.

OWS-00411: invalid SOAP envelope content
Category:: WebService
Cause:: The content of the soap envelope is invalid.
Action:: Correct the content of the soap envelope.

OWS-00412: invalid SOAP envelope
Category:: WebService
Cause:: The root element of the message is not a soap envelope.
Action:: Make the root element a valid soap envelope.

OWS-00413: SOAP envelope version mismatch
Category:: WebService
Cause:: The namespace or the version of the envelope is not correct.
Action:: Correct the namespace of the soap envelope.

OWS-00414: Caught exception while handling request: {0}
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-00415: Caught exception while preparing response: {0}
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-00416: Caught exception while invoking the post handling hook: {0}
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-00417: Internal Server Error ({0})
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-00418: Could not find the field in the Holder that contains the Holder value: {0}
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-00420: No jar file (or directory) found at specified path: {0}
Category:: WebService
Cause:: The specified jar file does not exist.
Action:: Check if the jar file name is correct and it is in the right directory.

OWS-00422: Exception occured while verifiying EJB: Class: {0} Details: {1}
Category:: WebService
Cause:: Error while parsing ejb-jar.xml. Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-00423: The EJB {0} was not found in the specified ejb location
Category:: WebService
Cause:: The ejb-jar.xml does not contain the specified EJB.
Action:: Check if the name of the EJB is correct and it is present in the ejb-jar.xml.

OWS-00425: Unable to locate ejb-jar.xml in {0}
Category:: WebService
Cause:: The application does not contain an ejb-jar.xml deployment descriptor file. The deployment descriptor file is inspected to locate the endpoint service interface
Action:: Add ejb-jar.xml and reassemble the application.

OWS-00426: Error parsing ejb-jar.xml. No session beans found.
Category:: WebService
Cause:: The application does not contain any session bean definition. The business functions to be exposed as webservices should be defined in a session bean.
Action:: Write an Enterprise Java Session Bean that contains the business functions that you want to expose.

OWS-00427: Error parsing ejb-jar.xml. Stateful session beans are not supported.
Category:: WebService
Cause:: Creating webservices from a stateful session bean is not supported. The business functions to be exposed as webservices should be defined in a stateless session bean.
Action:: Remove the stateful session bean, write a stateless session bean that contains the business functions that you want to expose.

OWS-00432: ERROR: {0}
Category:: WebService
Cause:: Server or client artifacts generation has failed.
Action:: This is a generic error indicating an error condition. You should also see a message describing the details.

OWS-00433: WARNING: {0}
Category:: WebService
Cause:: Server or client artifacts generation has encountered a possible error.
Action:: This is a generic warning. You should also see a message describing the details.

OWS-00436: -import requires a WSDL-based configuration file
Category:: WebService
Cause:
Action:

OWS-00437: -define requires a service-based configuration file
Category:: WebService
Cause:
Action:

OWS-00439: You have specified : -gen:both or -gen:client with SEI. The use of these modes are recommended with WSDL only.
Category:: WebService
Cause:
Action:

OWS-00442: Problem validating implementation class. {0}
Category:: WebService
Cause:: Supplied Service implementation class is not valid. It could be that the implementation class does not implement the interface correctly or it does not conform to JAXRPC requirements or the class is not found.
Action:: Make sure the implementation class is JAXRPC compliant if it is a JAXRPC webservice; make sure the classpath containing the implementation class is correctly specified

OWS-00450: parsing failed: {0}
Category:: WebService
Cause:: SAXException is thrown from the parser while parsing the WSDL.
Action:: Fix the WSDL according to the error reported by the parser.

OWS-00451: parsing failed: {0}
Category:: WebService
Cause:: ParserConfigurationException is thrown from the parser while parsing the WSDL.
Action:: Unexpected internal error.

OWS-00460: Element type "{1}" is missing required attribute "{0}"
Category:: WebService
Cause:: The WSDL or Schema entity is missing the required attribute.
Action:: Add the required attribte with a valid value to the WSDL or Schema entity.

OWS-00461: Element named "{0}" of type "{2}" is missing required attribute "{1}"
Category:: WebService
Cause:: The WSDL or Schema entity is missing the required attribute.
Action:: Add the required attribte with a valid value to the WSDL or Schema entity.

OWS-00463: missing required sub-entity "{0}" of element "{1}"
Category:: WebService
Cause:: A sub-element required by the schema or WSDL specification is missing.
Action:: Modify the schema or WSDL to add the required sub-element.

OWS-00464: Could not find Attribute : "{0}"
Category:: WebService
Cause:: An attribute reference is not defined in the schema.
Action:: Modify the schema to define the missing attribute reference.

OWS-00465: Unsupported schema feature : "{0}"
Category:: WebService
Cause:: An element defined in the schema is not supported by the system.
Action:: Modify the schema.

OWS-00466: The element is not supported in this context : "{0}"
Category:: WebService
Cause:: A sub-element of the complex type extension/restriction definition in the schema is not supported by the system.
Action:: Modify the complex type extension/restriction definition in the schema.

OWS-00467: Unsupported simple type definition : "{0}" inside "{1}" element
Category:: WebService
Cause:: A simple type defined in the schema is not supported by the system.
Action:: Modify the simple type to a simple type supported by the system.

OWS-00468: invalid sub-element "{0}" of element "{1}"
Category:: WebService
Cause:: The WSDL contains an element with a sub-element that is not supported by the system. Check WSDL 1.1 specification.
Action:: Modify the invalid sub-element based on the WSDL 1.1 specification.

OWS-00469: invalid attribute "{0}" of element "{1}"
Category:: WebService
Cause:: The WSDL or schema contains an element with an attribute that is either formatted incorrectly or does not comply with the specifications support by the system. The specifications to check include SOAP, WSDL 1.1 and jaxrpc.
Action:

OWS-00470: invalid value "{1}" for attribute "{0}"
Category:: WebService
Cause:: A attribute on a WSDL or schema element has a value that is not expected by the system.
Action:: or WSDL to comply with the value for the schema type of the attribute or change the type of the attribute to a simple type like string or int.

OWS-00471: invalid range found (min: {0}, max: {1})
Category:: WebService
Cause:: A complex type in a schema defines min and max occurance on a type that the system does not support.
Action:: Change the max occurances attribute to 1 so the system will except the schema.

OWS-00472: exclusive attributes: "{0}", "{1}"
Category:: WebService
Cause:: A complex type in a schema defines two attributes that are not supposed to be defined at the same time.
Action:: Remove one of the specified attriubutes from the schema.

OWS-00474: not a simple type: "{0}"
Category:: WebService
Cause:: A schema type other than a simple type was found in a schema when a simple type is expected.
Action:: Change the type specified in the error message to a simple schema type or change the reference to this type to a simple schema type.

OWS-00475: port type "{0}" in binding "{0}" not found.
Category:: WebService
Cause:: The specified WSDL is invalid or complete. A binding in a WSDL document has a reference to a portType that is not defined in the WSDL.
Action:: Change the value of the type attribute in the binding to the name of a portType that is defined in the WSDL.

OWS-00476: message "{0}" not found.
Category:: WebService
Cause:: The specified WSDL is invalid or complete. An input, output or fault element has a value for the message attribute that is not defined in the WSDL.
Action:: Change the value of the message attribute to a message that is defined in the WSDL.

OWS-00477: type "{0}" defined for the message part "{1}" could not found.
Category:: WebService
Cause:: The type definition is not found in the schema.
Action:: Add the type definition to the schema, or change the value of the type attribute to the name of an existing schema type.

OWS-00478: element "{0}" defined for the message part "{1}" could not found.
Category:: WebService
Cause:: A schema contains a reference to an element name that does not exist in the specified set of schemas. The set of schemas can be inside of a WSDL document, imported from a WSDL document or imported from other schema documents.
Action:: Change the reference to an element name that is found in the specified set of schemas, or define the type in the schema.

OWS-00480: Binding "{1}" used in port "{0}" not found.
Category:: WebService
Cause:: The specified WSDL is invalid or complete. A port in the WSDL document has a reference to a binding that is not defined in the WSDL.
Action:: Change the value of the binding attribute in the port to the name of a binding that is defined in the WSDL, or define the binding.

OWS-00481: The name "{0}" is not a valid XML NCName. (see http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName)
Category:: WebService
Cause:: The name is not a valid XML NCName.
Action:: Correct the value of NCName. See http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName for the format.

OWS-00482: The extensibility element "{0}" is unknown and has a wsdl:required attribute set to "true"
Category:: WebService
Cause:: During WSDL validation, found unrecognized extensibility element with wsdl:required attribute set.
Action:: Ensure required extension registry is set with WSDLReader when reading WSDL document into WSDL definition or remove wsdl:required attribute

OWS-00483: The WSDL contains a mixture of styles - "document" and "rpc". Only "rpc" OR "document" is supported in a WSDL, not both.
Category:: WebService
Cause:: WSDL contains a mixture of styles i.e both "Document" and "Rpc" style operation
Action:: Multiple styles WSDL is not supported by JAXRPC/JAXWS. Make sure WSDL does not contain muplitple styles i.e both document and rpc style bidning operation.

OWS-00484: The WSDL contains a mixture of uses - "literal" and "encoded". Only "literal" OR "encoded" is supported in a WSDL, not both.
Category:: WebService
Cause:: WSDL contains both "literal" and "encoded" use
Action:: Make sure WSDL does not contain mixture of uses - "literal" and "encoded". Only "literal" or "encoded" is supported in a WSDL, not both

OWS-00485: Operation "{0}" and "{1}" have conflicting SOAPAction values. Do not overload any operation or give unique SOAPAction value to each operation binding.
Category:: WebService
Cause:: Two or more operations specified in WSDL have conflicting SOAPAction values.
Action:: Do not overload any operation or give unique SOAPAction value to each operation binding.

OWS-00486: Operation "{0}" does not have a SOAPAction value. Give it a unique value.
Category:: WebService
Cause:: In WSDL, overloaded operation does not contain SOAPAction value.
Action:: Specify unique SOAPAction value for the overloaded operation.

OWS-00487: Element does not have name
Category:: WebService
Cause:: Element declared in schema does not have a "name" attibute set.
Action:: Specify a name to an Element defined in a schema.

OWS-00488: Attribute group does not have name
Category:: WebService
Cause:: Attribute group does not contain any name.
Action:: Specify a name to an attribute group.

OWS-00490: AttributeGroup "{0}" child missing ref attribute.
Category:: WebService
Cause:: Child element of Attirbute group is missing "ref" attribute.
Action:: Specify a name to a child element of Attibute group.

OWS-00491: Attribute declaration missing name.
Category:: WebService
Cause:: In schema, attirbute declaration is missing name.
Action:: Provide valide "name" to the attribute declaration.

OWS-00492: AttributeGroup missing ref attribute
Category:: WebService
Cause:: During schema validation, found AttributeGroup element is missing "ref" attribute.
Action:: Make sure AttributeGroup has "ref" attribute declared.

OWS-00493: Warning: {0} is already defined. Ignoring.
Category:: WebService
Cause:
Action:

OWS-00494: The portType {0} is used by two bindings with different headers mapped to parameters. This usecase is not supported at this time. Map the same headers to parameters for all bindings using this port type.
Category:: WebService
Cause:: The portType defined in WSDL is used by two bindings with different headers mapped to parameters.
Action:: Map the same headers to parameters for all bindings using this port type.

OWS-00495: The specified service name "{0}" was not found.
Category:: WebService
Cause:: In WSDL, service element does not have "name" attirbute defined.
Action:: Make sure WSDL has valid service name.

OWS-00496: Error while loading the schemas defined in WSDL "{0}": "{1}"
Category:: WebService
Cause:: Failed to load the schema specified in the WSDL.
Action:: Ensure the schema location specified in the WSDL is correct.

OWS-00499: LiteralArrayWrapper may only have one element member.
Category:: WebService
Cause:: LiteralArrayWrapper has more than one element member.
Action:: Make sure LiteralArayWrapper contains one element member.

OWS-00500: The annotation type or property "{0}" has been deprecated in this version of Oracle WebServices.
Category:: WebService
Cause:
Action:

OWS-00502: The annotations on the impl bean {0} or a referenced SEI are not consistent with the portType(s), binding(s) and service(s) in the WSDL specified by the wsdlLocation: {1}. Please refer to section 4.1.1 of the JSR-181 specification for details on the usage of wsdlLocation. The {2} was not found in the WSDL.
Category:: WebService
Cause:: The WSDL specified by a wsdlLocation attribute is inconsistent with the portType and bindings declared in the same WSDL.
Action:: Ensure that the annotations are consistent with the WSDL. See section 4.1.1 of the JSR-181 spec.

OWS-00505: Not a java bean
Category:: WebService
Cause:: The specified value type is not a valid Java Bean.
Action:: Ensure that the all declared value types are valid Java Bean.

OWS-00506: Not a java bean. Class is not public.
Category:: WebService
Cause:: The specified class is not a valid Java Bean.
Action:: Ensure the specified class has "public" modifier.

OWS-00526: Not in class path
Category:: WebService
Cause:: The specified class could not found in classpath.
Action:: Ensure that all required classes or jar files containing classes are declared in classpath.

OWS-00527: Element "{0}" can not have both a type attribute and a nested type declaration.
Category:: WebService
Cause:: The WSDL or schema contains an element with a type attribute and a nested type defined.
Action:: None

OWS-00528: Type "{0}" is not a valid JAXRPC value type or it is not serializable.
Category:: WebService
Cause:: SEI contains method with unserializable return type or parameter type
Action:: Ensure that all parameter types and return type are valid value types as per JAXRPC specification.

OWS-00530: WSDL is not WS-I BP compliant. Literal style WSDL at location "{0}" can not have soap encoded type.
Category:: WebService
Cause:: Invalid WSDL. Provided WSDL has both literal and soap encoding style.
Action:: Make sure WSDL has either "literal" or "encoding" style, NOT both

OWS-00531: Could not find schema from URL source, file source, classpath or application context at this lcoation: "{0}"
Category:: WebService
Cause:: Could not locate the schema document from file, url, classpath or application context.
Action:: Verify that the specified location of schema is correct.

OWS-00532: Failed to retrieve policy
Category:: WebService
Cause:: Could not retrieve the policy from the Policy Accessor.
Action:: System Internal Error - Contact Oracle Support Services

OWS-00533: Value {0} is not valid for {1}
Category:: WebService
Cause:: Invalid value encountered while deserializing a Java value from XML.
Action:: Verify that XML datatype contains valid value as per the schema.

OWS-00536: The output of a binding operation "{0}" is missing
Category:: WebService
Cause:: The output of a binding operation is missing.
Action:: Verify that the output element is properly specified in the binding operation in the WSDL.

OWS-00537: The input element, under namespace of "http://schemas.xmlsoap.org/wsdl/", of the binding operation "{0}" is missing
Category:: WebService
Cause:: The input element, under namespace of "http://schemas.xmlsoap.org/wsdl/", of a binding operation is missing.
Action:: Verify that the input element is properly specified in the binding operation in the WSDL.

OWS-00538: The value of the BindingType annotation "{0}" does not match the SOAP version "{1}" on the WSDL.
Category:: WebService
Cause:: The value of the BindingType annotation does not match the SOAP version on the WSDL.
Action:: Verify the value of the BindingType annotation.

OWS-00539: The WebParam or WebResult annotation on method "{0}" does not match the WSDL or Schema; The "{1}" "{2}" element is missing.
Category:: WebService
Cause:: The WebParam or WebResult annotation does not exist, or does not match the WSDL/Schema.
Action:: Verify the value of the WebParam or WebResult annotation.

OWS-00542: Unable to initialize, missing WebServicesProcessor
Category:: WebService
Cause:: Unable to initialize interceptors due to missing WebService Processor
Action:: System Internal Error - Contact Oracle Support Services

OWS-00543: Unable to provision web service, cannot read WSDL. Error: {0}
Category:: WebService
Cause:: Could not read WSDL.
Action:: Check the WSDL URL for correctness and try again or check the server logs for details.

OWS-00544: Error destroying interceptors {0}
Category:: WebService
Cause:
Action:

OWS-00545: Unable to read SOAP message {0}
Category:: WebService
Cause:
Action:

OWS-00546: Invalid port configuration {0}
Category:: WebService
Cause:
Action:

OWS-00547: {0}
Category:: WebService
Cause:
Action:

OWS-00549: The WSDL has overloaded operations "{0}".
Category:: WebService
Cause:: The WSDL has overloaded operations.
Action:: Avoid using overloaded operations.

OWS-00550: JDK1.5 enum is not supported "{0}".
Category:: WebService
Cause:: JDK1.5 enum is not supported
Action:: Provide a custom seriallizer.

OWS-00551: You are running on JDK6 which comes with JAX-WS 2.1 API and JAXB 2.2 API, but this tool requires JAX-WS 2.2 API and JAXB 2.2.1 API. Use the endorsed standards override mechanism (http://java.sun.com/javase/6/docs/technotes/guides/standards/).
Category:: WebService
Cause:: JDK 1.6 not configured correctly for JAX-WS
Action:: Provide an endorsed folder with the newer jars

OWS-03002: Failed to load wsm config schema: {0}
Category:: WebService
Cause:: Failed to load wsm config schema.
Action:: Please check the WSM configuration schema.

OWS-03003: {0}
Category:: WebService
Cause:
Action:

OWS-03004: {0}
Category:: WebService
Cause:: An exception occured while webservice management configuration.
Action:: Verify that the oracle proprietary descriptor for configuration is valid xml file and confirms to the schema "http://xmlns.oracle.com/oracleas/schema/11/oracle-webservices-client-11_1.xsd"

OWS-03005: Unable to connect to URL: {0} due to {1}
Category:: WebService
Cause:
Action:

OWS-03009: Error reading client wsmgmt configuration {0}
Category:: WebService
Cause:: Unexpected error occurs while reading client configuration file
Action:: NONE

OWS-03010: Error creating default client wsmgmt configuration {0}
Category:: WebService
Cause:: Unexpected error occured while creating default client side configuration file
Action:: System Internal Error - Contact Oracle Support Services

OWS-03011: Error parsing client wsmgmt configuration file {0}
Category:: WebService
Cause:
Action:

OWS-03012: Error parsing client wsmgmt configuration file {0}
Category:: WebService
Cause:
Action:

OWS-03013: Error parsing client wsmgmt configuration file {0}
Category:: WebService
Cause:: Unexpected error occured while parsing client webservice management configuration file
Action:: Verify that client side configuration file is a valid xml file

OWS-03014: Error loading policy access cache configuration {0}
Category:: WebService
Cause:: Policy access cache configuration file could not be loaded due to unexpected error
Action:: System Internal Error - Contact Oracle Support Services

OWS-03015: Error accessing policy from cache {0}
Category:: WebService
Cause:: Accessing policy from cache is failed
Action:: System Internal Error - Contact Oracle Support Services

OWS-03016: Error loading interceptor class {0}
Category:: WebService
Cause:: Failed to looad the Inteceptor class
Action:: Ensure all required webservices client side jar files available in classpath

OWS-04007: Error in system configured ejb prehandler: {0}
Category:: WebService
Cause:
Action:

OWS-04011: Error in resolving the webservice endpoint: {0}
Category:: WebService
Cause:: Failed to determine the WebService Endpoint for the servlet
Action:: None

OWS-04014: Error in system configured servlet post-handler: {0}
Category:: WebService
Cause:
Action:

OWS-04018: Error processing soap message over jms :{0}
Category:: WebService
Cause:
Action:

OWS-04020: Error during handler invocation:
Category:: WebService
Cause:
Action:

OWS-04024: Error in system configured ejb post-handler: {0}
Category:: WebService
Cause:
Action:

OWS-04026: An I/O error occurred for port: {0}: {1}.
Category:: WebService
Cause:: An unexpected IO error occured while processing service request.
Action:: None

OWS-04029: Error in system configured servlet pre-handler: {0}
Category:: WebService
Cause:
Action:

OWS-04039: Error closing connection: {0}
Category:: WebService
Cause:: Failed to close the connection to specific database
Action:: None

OWS-04042: Error happened while loading the DDs
Category:: WebService
Cause:
Action:

OWS-04043: {0}
Category:: WebService
Cause:
Action:

OWS-04044: The referenced wsdl file has changed, please re-deploy {0}
Category:: WebService
Cause:
Action:

OWS-04045: Malformed Request Message: {0}
Category:: WebService
Cause:: Received malformed SOAP request message
Action:: Ensure the correct SOAP message constructed at client side

OWS-04046: {0} {1}
Category:: WebService
Cause:: A server side fault occured while handling the SOAP message
Action:: Please see the exception or server side log for more detail

OWS-04047: Cannot create xslt transformer
Category:: WebService
Cause:
Action:

OWS-04048: xslt transformation failed
Category:: WebService
Cause:
Action:

OWS-04050: Unable to load the webservices management interceptor pipeline
Category:: WebService
Cause:
Action:

OWS-04061: Internal JMX error {0}
Category:: WebService
Cause:: Internal error while configuring JMX
Action:: None

OWS-04062: XML parser configuartion error {0}
Category:: WebService
Cause:: An unexpected error occured while parsing configuring the XML parser
Action:: None

OWS-04065: Error creating default port configuration for interceptor {0}
Category:: WebService
Cause:: The default port configuration for interceptor could not be created
Action:: None

OWS-04066: Missing port info for service.
Category:: WebService
Cause:: The Port information for the service is missing
Action:: Add the necessary port information while configuring dynamic service.

OWS-04067: Error reading config file {0}
Category:: WebService
Cause:: Failed to read the interceptor configuration file
Action:: None

OWS-04068: Error serializing default config {0}
Category:: WebService
Cause:: Failed to serialize the default configuration for interceptor.
Action:: None

OWS-04069: Error serializing global configuration for {0} interceptor {1}
Category:: WebService
Cause:: Failed to serialize global configration for interceptor.
Action:: None

OWS-04070: Error serializing configuration {0}
Category:: WebService
Cause:: Failed to serialize the configuration
Action:: None

OWS-04071: Unrecognized interceptor configuration: {0}
Category:: WebService
Cause:
Action:

OWS-04072: Error writing config file {0}
Category:: WebService
Cause:: Error writing the configuration file for interceptor to FileManager
Action:: None

OWS-04073: Error parsing wsmgmt configuration file {0}
Category:: WebService
Cause:
Action:

OWS-04074: Error parsing wsmgmt configuration file {0}
Category:: WebService
Cause:
Action:

OWS-04075: Error parsing wsmgmt configuration file {0}
Category:: WebService
Cause:
Action:

OWS-04086: {0}
Category:: WebService
Cause:: An unexpected error occured
Action:: None

OWS-04092: Unable to configure parser: {0}
Category:: WebService
Cause:
Action:

OWS-04093: Unable to parse schema: {0}
Category:: WebService
Cause:
Action:

OWS-04094: unknown tag <{0}> in {1}
Category:: WebService
Cause:
Action:

OWS-04097: Error creating client default port configuration for interceptor {0}
Category:: WebService
Cause:: Failed to create client default port configuration for interceptor
Action:: None

OWS-04100: Unable to find provider port that is associated with the servlet named {0}. Please make sure <provider-name>{0}</provider-name> exists in oracle-webservices.xml.
Category:: WebService
Cause:
Action:

OWS-04101: Unable to add dynamic provider endpoint. Please make sure service name {0} and port name {1} are unique. They are specified as arguments to the ProviderConfig.addService() method or in the endpoint associated WSDL.
Category:: WebService
Cause:
Action:

OWS-04102: Unable to configure dynamic provider endpoint across cluster due to exception {0}
Category:: WebService
Cause:
Action:

OWS-04103: Unknown element <{0}> in descriptor: {1}
Category:: WebService
Cause:
Action:

OWS-04104: The oracle-webservices.xml configuration references a web service description named "{0}", but there is no web service description with that name in webservices.xml.
Category:: WebService
Cause:
Action:

OWS-04105: The final WSDL path "{0}" cannot be parsed as a URL: {1}
Category:: WebService
Cause:: The URL path for the final WSDL is not valid
Action:: Provide the valid URL location for the WSDL.

OWS-04106: The value of the element named "{0}" ({1}) in {2} is invalid. Please refer to the XML schema of this descriptor for acceptable values.
Category:: WebService
Cause:: Found invalid value of an element declared in webservice deployment descriptor
Action:: Please refer to the XML schema of this descriptor for acceptable values for this element.

OWS-04107: The proprietary implementor type is not specified.
Category:: WebService
Cause:
Action:

OWS-04108: An error was encountered while trying to write the runtime configuration for the web service endpoint named "{0}": {1}
Category:: WebService
Cause:: An error was encountered while trying to write the runtime configuration for the web service endpoint.
Action:: None

OWS-04110: Error downloading import: Invalid URL
Category:: WebService
Cause:: The specified URL for the imported WSDL is invalid
Action:: Provide the correct URL location for the WSDL import

OWS-04111: Proxy information not set, external import downloads may fail.
Category:: WebService
Cause:
Action:

OWS-04112: The policy accessor configuration could not be loaded from {0}: {1}. Using default configuration instead.
Category:: WebService
Cause:: Failed to load policy accessor configuration
Action:: No action required as incase of this, default policy accessor configuration will be used

OWS-04113: Policy advertisement failed for {0}: {1}
Category:: WebService
Cause:: Failed to advertise the policy in the WSDL
Action:: None

OWS-04115: An error occurred for port: {0}: {1}.
Category:: WebService
Cause:: A server side exception occured while processing request or creating the response message
Action:: Please see the server side log for the detail.

OWS-04116: The error stack trace: {0}
Category:: WebService
Cause:
Action:

OWS-04117: {0}
Category:: WebService
Cause:: Exception occured while configuring dynamic provider based endpoint
Action:: None

OWS-04119: Local service registration failed for {0}: {1}
Category:: WebService
Cause:
Action:

OWS-04121: Invalid use of <web-site> element in oracle-webservices.xml.<web-site> element must have two attributes "host" and "port" with valid values
Category:: WebService
Cause:: <web-site> element of oracle-webservice.xml doesn't contain 'host' and 'port' attributes with valid values
Action:: Add valid 'host' and 'port' attributes to the <web-site> element, or remove the element.

OWS-04123: Unsupported oracle-webservices deployment descriptor for module {0}, schema version {1}
Category:: WebService
Cause:
Action:

OWS-04124: Failed to register the web service Config MBeans for application: {0} endpoint: {1} the error is: {2}
Category:: WebService
Cause:: Failed to register the web service config MBeans for endpoint
Action:: None

OWS-04125: cannot find WSDL definition required to validate input
Category:: WebService
Cause:: cannot load web service WSDL definition, which is required for schema validation of input
Action:: Ensure that the WSDL is available, or set schema validation of input to false

OWS-04126: Input Violates Schema
Category:: WebService
Cause:: SOAP body element of the input message cannot be validated against schema in the WSDL
Action:: Correct input message body, input message type in the WSDL schema, or set schema validation of input to false

OWS-04127: Invalid query string
Category:: WebService
Cause:: User has specified invalid URL Query String.
Action:: Verify that the correct query string is specified for acccessing the testpage.

OWS-04128: Failed to deploy/initialize the application as given archive is missing required standard webservice deployment decriptor.
Category:: WebService
Cause:: The user suppplied war archive is missing required webservice deployment descriptor
Action:: Create WAR file with required webservice deployment descriptor or use WSA's jaxwsAssemble command to assemble the WAR file.

OWS-04130: Failed to initialize Tie class "{0}" at runtime due to Error: {1}
Category:: WebService
Cause:: Failed to initialize the tie class on server side due to classloading issue or java security.
Action:: Please look the server log for exact cause of an error.

OWS-04131: SOAP must understand error. MustUnderstand headers:["{0}"] are not understood.
Category:: WebService
Cause:: Server could not understand SOAP header which has mustUnderstand flag set to true.
Action:: Please look the SOAPFault string for any detail message and check the client and server side configuration.

OWS-04132: FastInfoset is disabled for this service
Category:: WebService
Cause:: A FastInfoset message was received for a service that has FastInfoset disabled
Action:: Please enable FastInfoset for the web service or send a non-FastInfoset input message

OWS-04136: JRF WebServices are not supported in 'Restricted JRF'.
Category:: WebService
Cause:: Trying to deploy JRF WebServices which is not supported in 'Restricted JRF'.
Action:: Use 'Full JRF' for deploying application that uses JRF WebServices implementation.

OWS-04137: DTD is not supported
Category:: WebService
Cause:: Sending SOAP request with DTD
Action:: Do not use DTD in SOAP request to JRF web services

OWS-08008: Web service artifact generation failed.
Category:: WebService
Cause:: Web service artifact generation failed.
Action:: Verify and correct by the error message and stack trace.

OWS-08010: Incorrect packaging ({0}): WSDL should be packaged in a directory named either 'META-INF/wsdl' or 'WEB-INF/wsdl'.
Category:: WebService
Cause:: Incorrect WSDL packaging.
Action:: Verify that the correct the WSDL packaging configurations.

OWS-08015: No web service named '{0}' is defined. Ignoring the proprietary configuration for this web service.
Category:: WebService
Cause:: Web service name is not properly defined.
Action:: Verify that the web service name from the proprietary configuration.

OWS-15001: An extension registry was not found for the element type ''{0}''
Category:: WebService
Cause:: An extension registry was not found for an element type
Action:: None

OWS-15002: A failure occurred in loading WSDL from ''{0}''
Category:: WebService
Cause:: A failure occurred in loading WSDL
Action:: Verify if the WSDL exists at the specified URL

OWS-15004: WSDL contains an operation type of ''{0}'' which is not supported for port type ''{1}''
Category:: WebService
Cause:: WSDL contains an operation type that is not supported
Action:: Modify the WSDL and change the operation type to a supported one

OWS-15005: An error occurred when invoking the method. Type of WSIF invocation was ''{1}'' and method name was (''{0}'')
Category:: WebService
Cause:: An error occurred when invoking the method
Action:: Check client code and network connection

OWS-15006: Multiple WSIFProvider found supporting the same namespace URI ''{0}''. Found (''{1}'')
Category:: WebService
Cause:
Action:

OWS-15008: WSIFDefaultCorrelationService removing correlator due to timeout. ID:''{0}''
Category:: WebService
Cause:
Action:

OWS-15010: Exception thrown while processing asynchronous response - ''{0}''
Category:: WebService
Cause:: Exception thrown while processing asynchronous response
Action:: None

OWS-25106: Internal error: {0}
Category:: WebService
Cause:
Action:

OWS-25108: Some messages have not been acknowledged
Category:: WebService
Cause:
Action:

OWS-25111: Error sending LastMessage: {0}
Category:: WebService
Cause:: Unknown
Action:: Check server logs for additional details.

OWS-25112: The WS-RM client interceptor encountered an exception while handling a response, {0}
Category:: WebService
Cause:
Action:

OWS-25113: Duplicate eliminated for message #{0}
Category:: WebService
Cause:
Action:

OWS-25118: Skip null in handling outbound message {0}
Category:: WebService
Cause:
Action:

OWS-25119: Forcing wsa:Action inside RM code to {0}. Please, verify your addressing handler configuration
Category:: WebService
Cause:
Action:

OWS-25168: An attempt was made to terminate a WS-RM sequence inactivity monitor for the sequence identified by {0}, which is not currently being monitored.
Category:: WebService
Cause:
Action:

OWS-50001: The @WebService.portName is not allowed on endpoint interfaces.: {0}
Category:: WebService
Cause:
Action:

OWS-50002: The @WebService.serviceName is not allowed on endpoint interfaces.: {0}
Category:: WebService
Cause:
Action:

OWS-50003: Could not find schema type : {0}
Category:: WebService
Cause:
Action:

OWS-50004: The method "{0}" does not have the AsyncHandler type parameter.
Category:: WebService
Cause:: The callback type asynchronous method that returns java.util.concurrent.Future must have the last parameter of the type AsyncHandler.
Action:: Add the last parameter of type AsyncHandler in the method, or regenerate the interface using wsa tool.

OWS-50005: Exception while retrieving the soap message from the internal callback handler.
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-50006: Could not deserialize the soap message to get the return value
Category:: WebService
Cause:: Refer to the details of the message for further information on possible causes.
Action:: Refer to the details of the message for further information on possible actions.

OWS-50007: Could not create the instance of asynchronous response bean of type "{0}"
Category:: WebService
Cause:: Cound not create the response Refer to the details of the message for further information on possible causes.
Action:: Check if the bean has a default constructor and the constructor is accessible.

OWS-50008: Cound not set the field ''{0}'' in the object of type ''{1}''.
Category:: WebService
Cause:: Possible causes are invalid field name, abcense of setter, inaccessible setter or mismatched field type.
Action:: Correct the bean class based on the details of the message.

OWS-50009: The method "{0}" must have a parameterized return type.
Category:: WebService
Cause:: The return type must be parameterized with the ResponseBean or the actual return type of the web service call.
Action:: Add the appropriate return type as the parameter of the AsyncHandler parameter. Or use the JAX-WS artifacts generation tools to generate the proper interface of asynchronous methods.

OWS-50010: Dispatch currently does not support REST style service.
Category:: WebService
Cause:: The AsyncHandler parameter must be parameterized with the ResponseBean or the actual return type of the web service call.
Action:: Add the appropriate return type as the parameter of the Response. Or use the JAX-WS artifacts generation tools to generate the proper interface of asynchronous methods.

OWS-50011: Dispatch currently does not support REST style service.
Category:: WebService
Cause:: The REST request cannot be processed via Dispatch. The feature is not yet supported.
Action:: Construct an HTTP Request for a RESTful webservice.

OWS-50012: Could not determine the soap version from the BindingType annotation''s value "{0}". Assuming SOAP version as 1.1
Category:: WebService
Cause:: The value of the BindingType annotation is invalid.
Action:: Use one of the valid values for the BindingType annotation. Refer to the documentation of javax.xml.ws.BindingType.

OWS-50013: Could not determine a valid protocol binding to generate for the binding public static final String {0}. A SOAP 1.1 binding will be the only protocol binding generated in the WSDL.
Category:: WebService
Cause:: The value of the BindingType is not supported or is invalid
Action:: Only SOAP and HTTP protocols are supported. Refer to the documentation or JAX-WS specification for valid values for javax.xml.ws.BindingType.

OWS-50014: Both @Deployment.restSupport() and @BindingType(javax.xml.ws.http.HTTPBinding.HTTP_BINDING) were specified. Only the latter will be used.
Category:: WebService
Cause:: Both the @Deployment.restSupport() and @BindingType(javax.xml.ws.http.HTTPBinding.HTTP_BINDING) were provided.
Action:: @Deployment.restSupport() has been deprecated. It should not be used. Use @BindingType(javax.xml.ws.http.HTTPBinding.HTTP_BINDING) instead.

OWS-50015: The given ws-addressing namespace "{0}" is not one of the supported wsa versions.
Category:: WebService
Cause:: The input ws addressing version is not supported
Action:: Correct the addressing version to use 2003/03 or 2004/08 or 2005/08.

OWS-50016: IOException converting AddressingInfo to public static final String.
Category:: WebService
Cause:: IO error converting addressing info to public static final String
Action:: correctAddressingInfo

OWS-50017: Port Metadata missing from the given callback interface class.
Category:: WebService
Cause:: Metadata such as port name or targetnamespace can not be found from the given input class.
Action:: Add the needed annotation to the interface class.

OWS-50018: The file "{0}" does not exist.
Category:: WebService
Cause:: The file name specified in syncInterfaceFileName could not be opened.
Action:: Check if the file name is correct and it exist.

OWS-50019: The file "{0}" should have some class or interface defined.
Category:: WebService
Cause:: The syncInterfaceFileName is not containing any class.
Action:: Check if the file has any class defined. Make sure that the file is compilable and so free of errors.

OWS-50020: There is no method in the file "{0}" to convert to asynchronous method.
Category:: WebService
Cause:: The interface file should have at least one method defined.
Action:: Add the required methods in the interface file.

OWS-50021: Cannot determine what methods to convert to asynchronous in file "{0}".
Category:: WebService
Cause:: The interface file has more than one method defined and no method name has been specified for conversion.
Action:: Please sepcify what methods need to be converted to asynchronous methods.

OWS-50022: The file "{0}" does not exist.
Category:: WebService
Cause:: The file name specified in asyncInterfaceFileName could not be opened.
Action:: Check if the file name is correct and it exist.

OWS-50023: The file "{0}" should have some class or interface defined.
Category:: WebService
Cause:: The asyncInterfaceFileName is not containing any class.
Action:: Check if the file has any class defined. Make sure that the file is compilable and so free of errors.

OWS-50024: Java Model is not set in the file system.
Category:: WebService
Cause:: The file system does not have any Java Model set.
Action:: Make sure that the file system has the Java Model set.

OWS-50025: JAX-WS endpoint bean has @SOAPBinding.use annotation that specifies the 'encoded' message format which is not supported in JAX-WS. JAX-WS 2.0 mandates 'literal' use only and supports either rpc/literal or document/literal style binding.
Category:: WebService
Cause:: In JAX-WS endpoint bean, @SOAPBinding.use annotation has 'encoded' value which is not supported in JAXWS
Action:: In JAX-WS endpoint bean, use either rpc/literal or document/literal style binding.

OWS-50026: Invalid use of @WebMethod annotation on method "{0}".As per JSR-181, if 'exclude' element is specified on @WebMethod annotation then other elements must not be specified with it.
Category:: WebService
Cause:: In JAX-WS endpoint bean, @WebMethod annotation has 'exclude' element that is used with other elements like 'action' or 'operationName' which is against the JSR-181 spec
Action:: Do not use 'action' or 'operationName' element if 'exclude' element is specified on @WebMethod annotation.

OWS-50027: @SOAPBinding annotation is only allowed on a method if SOAPBinding.style is "DOCUMENT". Method "{0}" specifies @SOAPBinding.style to "RPC" which is against JSR-181 so it will be ignored and default sytle "DOCUMENT/LITERAL" will be used.
Category:: WebService
Cause:: @SOAPBinding annotation at method level has 'rpc' style which is not valid as per JSR-181
Action:: Do not specify the 'rpc' style with @SOAPBinding annotation used at method level in JAX-WS enpoint interface/bean.

OWS-50028: The parameter/return type "{0}" in the method "{1}" is not supported. This method will not be exposed.
Category:: WebService
Cause:: The parameter/return type is NOT supported.
Action:: Do not use the unsupported JAVA Type in method parameter or return value.

OWS-50029: The method "{0}" has more than one input parameter that is not mapped to a header and style is BARE. This method will not be exposed.
Category:: WebService
Cause:: The java method has more than one input parameter that is not mapped to a header.
Action:: Map java parameters to a header using @WebParam annotation or use wrapped style operation.

OWS-50030: wsdlDocumentLocation is currently not supported.
Category:: WebService
Cause:: WSDLDocumentLocation is currently not supported
Action:

OWS-50031: Input address, serviceName and endpointName can not be all null
Category:: WebService
Cause:: ServiceName, PortName, or Address can not be all null.
Action:: Supply a non null argument for one of the parameters.

OWS-50032: Service name has not been specified for a non null port name.
Category:: WebService
Cause:: ServiceName can not be null when port name is specified.
Action:: Supply a non null service name.

OWS-50033: Exception occured building W3CEndpointReference.
Category:: WebService
Cause:: Exception occured when building W3C EndpintReference.
Action:: Verify that the Endpoint Reference address and other metadata to build W3C EndpointRefence are correct.

OWS-50034: The method "{0}" is ignored. {1}
Category:: WebService
Cause:: The JAVA method is ignored in WSDL generation.
Action:

OWS-50035: "{0}" cannot be used as parameter type or return value in "{1}".
Category:: WebService
Cause:: The JAVA type cannot be used as parameter type or return value in RPC-Literal and Document-Literal-BARE.
Action:

OWS-50036: Operations on portType should be unique, use @WebMethod(operationName="...") on java method "{0}" to resolve conflict.
Category:: WebService
Cause:: Operations the WSDL port type need to be unique.
Action:: Map non-unique JAVA method names to unique WSDL opeartion names using @WebParam(operation"...")

OWS-50037: Failed to load endpoint interface class "{0}" specified with @WebService.endpointInterface annotation in endpoint bean class "{1}". This may cause unexpected behavior like generated WSDL would be different from the expected one.
Category:: WebService
Cause:: Classloader failed to load the enpoint interface class that is implemented by the enpoint bean class
Action:: Check that the endpoint interface class is in the classpath

OWS-50038: Found "{0}" annotation on class "{1}" which is not allowed with PortableWebService endpoint class.
Category:: WebService
Cause:: User has specified the annotation on either webservice endpoint interface or implementation class which is not allowed with Portable WebService
Action:: Remove annotation which is not valid with @PortableWebService annotation.

OWS-50039: Could not load callback interface "{0}". Any methods defined in the interface will be ignored
Category:: WebService
Cause:: Callback interface class is not available or misspelt.
Action:: Make callback interface available.

OWS-50040: Failed while accessing Keystore details.
Category:: WebService
Cause:: Keystore details are not setup.
Action:: Configure keystore details for the server.

OWS-50042: [MessageID: {0}] Request MDB could not complete asynchronous request processing successfully. No response will be sent to the client. Analyze the details of the exception as it is likely server side configuration error.
Category:: WebService
Cause:: Asynchronous request processing resulted in exception
Action:: Analyze the exception and take appropriate action.

OWS-50043: JMS queue connection failed.
Category:: WebService
Cause:: JMS queues are not created, or wrong queue names are used.
Action:: Check that queues are created and referenced with the right names.

OWS-50044: [MessageID: {0}] Could not post async request message to the JMS queue.
Category:: WebService
Cause:: JMS queues are not created, or wrong queue names are used.
Action:: Check that queues are created and referenced with the right names

OWS-50045: Could not close the connection to JMS queue
Category:: WebService
Cause:: Internal error.
Action:: Can be ignored.

OWS-50047: [MessageID: {0}] No JMS queue specified for the request with non-anonymous replyTo for service "{1}"
Category:: WebService
Cause:: JMS queues are not created, or wrong queue names are used.
Action:: Check that queues are created and referenced with the right names

OWS-50048: ConnectionFactory for the destination "{0}" used for asynchronous service processing is not specified. Using default: "{1}"
Category:: WebService
Cause:: Connection factory is not specified.
Action:: Specify connection factory if default is not good.

OWS-50051: JMS queue for async service processing not found. Configure a JMS queue for this application.
Category:: WebService
Cause:: JMS queue are either not created or not correctly specified in the source annotations.
Action:: Verify that the JMS queues are created and the same are referred in the annotations in the service implementation class.

OWS-50056: Received a fault and user did not supply a fault listener. Details: "{0}"
Category:: WebService
Cause:: The web service implementation class does not have any methods annotated as FaultListener and either the input is fault, or the response from the callback service is fault.
Action:: Add the fault listener method if desired.

OWS-50057: Failed while re-creating the soap message from the JMS message
Category:: WebService
Cause:: System error
Action:: Analyze the exception reported in the log.

OWS-50058: Failed while re-creating the addressing header from the JMS message
Category:: WebService
Cause:: System error
Action:: Analyze the exception reported in the log.

OWS-50059: [MessageID: {0}] Error while processing the message off the JMS queue.
Category:: WebService
Cause:: System error
Action:: Analyze the exception details.

OWS-50061: Context is available locally. Should happen only while running in-process message listener.
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50062: [MessageID: {0}] Error while processing response. Will try the fault handler in web service implementation class.
Category:: WebService
Cause:: Callback service may be down or policy of the callback service is not matching with the callback client.
Action:: Analyze the exception details.

OWS-50064: [MessageID: {0}] Failed to send async response to client-side callback receiver.
Category:: WebService
Cause:: Callback service may be down, the callback URL may be wrong or callback service is not configured properly.
Action:: Verify the configuration of callback service and take action based on the details of exception.

OWS-50066: Could not save the context for async service in cache with the key "{0}".
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50067: Could not cleanup the context for async service from cache as it was not found.
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50069: Could not remove the saved context for async service from cache with the key "{0}".
Category:: WebService
Cause:: Internal system error
Action:: Internal system error.

OWS-50071: [MessageID: {0}] Error while trying the fault handler in web service implementation class.
Category:: WebService
Cause:: The fault handler method did not execute successfully.
Action:: Check the fault handler code.

OWS-50072: [MessageID: {0}] Got SOAPFaultException while executing the asynchronous operation
Category:: WebService
Cause:: This might be because of invalid request, missing resources in the service implementation or a bug.
Action:: Analyze the exception details.

OWS-50073: [MessageID: {0}] Encountered exception or error while invoking user's Java Web Service method.
Category:: WebService
Cause:: This might be because of invalid request, missing resources in the service implementation or a bug.
Action:: Analyze the exception or error details.

OWS-50080: [MessageID: {0}] Response MDB encountered exception during asynchronous response processing.
Category:: WebService
Cause:: Callback service is not up or it's configuration/policy is not matching with the async server.
Action:: Analyze the exception and configure the callback service.

OWS-50081: [MessageID: {0}] Response MDB encountered exception.
Category:: WebService
Cause:: Callback service is not up or it's configuration/policy is not matching with the async server.
Action:: Analyze the exception and configure the callback service.

OWS-50082: [MessageID: {0}] Response MDB will not retry sending response as callback service sent soap fault back. HTTP response code received by response MDB was "{1}".
Category:: WebService
Cause:: Callback service sent the fault back. Retrying may not help. There may be some configuration problem,
Action:: Analyze the fault and configure the client-side callback service properly.

OWS-50085: [MessageID: {0}] Could not create the user transaction for request processing.
Category:: WebService
Cause:: Internal system error.
Action:: Analyze the exception in the log.

OWS-50087: [MessageID: {0}] Could not begin the user transaction for request processing.
Category:: WebService
Cause:: Internal system error.
Action:: Analyze the exception in the log.

OWS-50088: [MessageID: {0}] Could not create user transaction for Web Method execution.
Category:: WebService
Cause:: Internal system error.
Action:: Analyze the exception in the log.

OWS-50090: [MessageID: {0}] Could not begin user transaction for Web Method execution.
Category:: WebService
Cause:: Internal system error
Action:: Analyze the exception in the log.

OWS-50092: [MessageID: {0}] Could not suspend the main transaction for executing the web method.
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50093: [MessageID: {0}] User transaction was marked for rollback after executing the web method.
Category:: WebService
Cause:: Web method execution marked the transaction for rollback.
Action:: It might be because of invalid input or a bug in the web method. Analyze the failure.

OWS-50094: [MessageID: {0}] Could not rollback the user transaction after executing the web method.
Category:: WebService
Cause:: Internal system error.
Action:: Analyze the exception in the log.

OWS-50095: [MessageID: {0}] User transaction is being rolledback after getting unexpected exception in executing the web method.
Category:: WebService
Cause:: Web method did not complete successfully.
Action:: It might be because of invalid input or a bug in the web method. Analyze the failure.

OWS-50096: [MessageID: {0}] User transaction is being rolled back after getting failure in getting response.
Category:: WebService
Cause:: There might be some problem with the callback service or its configuration.
Action:: Check if the callback service is up and configured properly.

OWS-50100: [MessageID: {0}] Could not get the transaction manager (javax.transaction.TransactionManager).
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50102: [MessageID: {0}] Could not resume the suspended main transaction.
Category:: WebService
Cause:: Internal system error
Action:: Internal system error.

OWS-50103: [MessageID: {0}] Rolled back a user transaction after executing the web method.
Category:: WebService
Cause:: There might be some problem with the callback service or its configuration.
Action:: Check if the callback service is up and configured properly.

OWS-50104: [MessageID: {0}] Could not rollback a user transaction after executing the web method.
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50106: [MessageID: {0}] Could not commit the user transaction for web method execution.
Category:: WebService
Cause:: Internal system error.
Action:: Analyze the related exception report in the log.

OWS-50107: [MessageID: {0}] Could not rollback the main transaction
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50108: [MessageID: {0}] Could not commit the main transaction
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50109: [MessageID: {0}] HTTP response code received from client-side callback service is "{1}".
Category:: WebService
Cause:: Callback service returned HTTP response other than 200 or 202.
Action:: Analyze the details of soap message returned by callback service or the HTTP error code.

OWS-50111: [MessageID: {0}] Received soap fault from the client-side callback service.
Category:: WebService
Cause:: Callback has sent a soap fault as the response.
Action:: Analyze the fault and configure the callback service properly.

OWS-50112: [MessageID: {0}] Could not dump the soap message
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50113: [MessageID: {0}] Could not create SSLSocketFactory.
Category:: WebService
Cause:: Keystore may not have been configured properly.
Action:: Configure the keystore details for the server.

OWS-50114: [MessageID: {0}] KeyStore file locations are not available. Configure it for the server to make the SSL work.
Category:: WebService
Cause:: Keystore may not have been configured properly.
Action:: Configure the keystore details for the server.

OWS-50115: Exception in handler chain
Category:: WebService
Cause:: Handler chain has thrown some exception
Action:: Look at the details of exception.

OWS-50117: Unsupported message context, jaxws handler will not be called
Category:: WebService
Cause:
Action:

OWS-50118: Unsupported message context, "{0}" could not handle fault
Category:: WebService
Cause:
Action:

OWS-50121: Error parsing handler chain: "{0}"
Category:: WebService
Cause:
Action:

OWS-50122: Could not process callback interface "{0}". Any methods defined in the interface will be ignored
Category:: WebService
Cause:
Action:

OWS-50123: Unsupported operation when generating schemas "{0}"
Category:: WebService
Cause:
Action:

OWS-50124: Unknown Exception when generating schemas: "{0}"
Category:: WebService
Cause:
Action:

OWS-50125: Could not load schema from location "{0}".
Category:: WebService
Cause:
Action:

OWS-50127: Could not determine wsdl ports.
Category:: WebService
Cause:
Action:

OWS-50128: Could not find service "{0}"; Using first service in WSDL instead.
Category:: WebService
Cause:
Action:

OWS-50129: No wsdl location or document specified
Category:: WebService
Cause:
Action:

OWS-50130: No web module with name of "{0}" so a new war will be created
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50131: Found web module with name of "{0}", so the generated contents will be merged.
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50132: Can not specify war argument and have an input be an ear that contains a war with a matching context root.
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50133: Error extracting war "{0}".
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50134: Error while processing ejb-jar.xml for ejb module at "{0}".
Category:: WebService
Cause:
Action:

OWS-50135: Could not load jaxrpc annotation parser, the webservices in this ejb will not be manageable
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50136: Multiple webservice descriptions in webservices.xml has the same port name "{0}" and service name "{1}", defaulting to webservice description named "{2}".
Category:: WebService
Cause:
Action:

OWS-50138: Could not write operation metadata for "{0}".
Category:: WebService
Cause:: Exception in writing operation metadata
Action:: Analyze the exception.

OWS-50139: HandlerChain configuration file: "{0}".
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50140: Failed to resolve HandlerChain annotation "file" value ({0}) as it is specified on "{1}"
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50141: Fabric Registration ignored because this service does not use SDO binding.
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50143: Fabric Registration ignored because Register class "{0}" can not be instantiated.
Category:: WebService
Cause:
Action:

OWS-50144: Fabric Registration ignored because Register class "{0}" can not be accessed.
Category:: WebService
Cause:
Action:

OWS-50146: Fabric Registration failed due to exception: "{0}".
Category:: WebService
Cause:
Action:

OWS-50147: SDO Type Registration failed due to exception: "{0}".
Category:: WebService
Cause:: TBD
Action:: TBD

OWS-50149: There is more than one webservice with the name of "{0}" this can cause problems at deployment or runtime. To resolve the conflict add a serviceName property to a WebService annotation
Category:: WebService
Cause:
Action:

OWS-50151: The service name "{0}" could not be found in the wsdl "{1}". Defaulting to the first service in the wsdl "{2}"
Category:: WebService
Cause:
Action:

OWS-50152: The port name "{0}" could not be found in the wsdl "{1}". Defaulting to the first port named "{2}" in the service named "{3}"
Category:: WebService
Cause:
Action:

OWS-50153: Multiple port components have the same service name "{0}" and port name "{1}", default to port component name "{2}".
Category:: WebService
Cause:
Action:

OWS-50154: Can not add partner links to wsdl because there are not two port types, actual number is "{0}".
Category:: WebService
Cause:
Action:

OWS-50155: Error processing handler chain: "{0}"
Category:: WebService
Cause:
Action:

OWS-50156: Unsupported type when generating schemas: "{0}"
Category:: WebService
Cause:
Action:

OWS-50159: [MessageID: {0}] Messages could not be read while cleaning up the asynchronous message queues. Exception: "{1}".
Category:: WebService
Cause:: System error
Action:: Internal error

OWS-50162: [MessageID: {0}] Request message was found in the queue while processing the response
Category:: WebService
Cause:: There might be a server/jvm crash after successful execution of business logic.
Action:: No action required.

OWS-50163: [MessageID: {0}] Response is not available. The web method execution did not complete or the response was lost.
Category:: WebService
Cause:: Response is not available. The web method execution did not complete or the response was lost.
Action:: Retry calling the method if it is safe to do so.

OWS-50177: Could not read saved context for async service from cache using the key: "{0}".
Category:: WebService
Cause:: Internal system error.
Action:: Internal system error.

OWS-50178: The password for the identity keystore could not be read from the security credential store while sending the response to the callback service. It should have been stored as key "{0}" in the map "{1}". Assuming no password is necessary.
Category:: WebService
Cause:: The password for the identity keystore is probably not saved in the security credentials or, the map or the key name may be wrong.
Action:: Save the password with appropriate key and the map as specified in the error.

OWS-50179: The password for recovering the key could not be read from the security credential store while sending the response to the callback service. It should have been stored as key "{0}" in the map "{1}". Assuming key password to be same as the identity keystore password.
Category:: WebService
Cause:: The password for the private key is probably not saved in the security credentials or, the map or the key name may be wrong.
Action:: Save the password with appropriate key and the map as specified in the error.

OWS-50180: The password for the trust keystore could not be read from the security credential store while sending the response to the callback service. It should have been stored as key "{0}" in the map "{1}". Assuming no password is necessary.
Category:: WebService
Cause:: The password for the trust keystore is probably not saved in the security credentials or, the map or the key name may be wrong.
Action:: Save the password with appropriate key and the map as specified in the error.

OWS-50181: Exception while accessing the password from the security credential store for using SSL while sending the response to the callback service.
Category:: WebService
Cause:: Internal system error.
Action:: Analyze the details of the exception

OWS-50183: Could not get the transaction manager using "{0}". Exception: "{1}"
Category:: WebService
Cause:: Method of getting transaction manager might have changed in this release.
Action:: Internal system error.

OWS-50184: Could not get the transaction manager using "{0}"Got unexpected class "{1}" instead of javax.transaction.TransactionManager.
Category:: WebService
Cause:: Method of getting transaction manager might have changed in this release.
Action:: Internal system error.

OWS-50187: [MessageID: {0}] System Error: Could not get the addressing namespace and so the None URI.
Category:: WebService
Cause:: Addressing namespace is not available.
Action:: Internal system error.

OWS-50198: The content negotiation strategy {0} is incompatible with a service that has FastInfoset disabled according to the WSDL
Category:: WebService
Cause:: The content negotiation strategy provided is incompatible with a Service that has FastInfoset Disabled
Action:: Do not supply a content negotiation strategy On the client

OWS-50199: The FastInfoset content negotiation strategy '{0}' specified in the request context property conflicts with the value '{1}' specified on the feature object
Category:: WebService
Cause:: The content negotiation request context property provided conflicts with the content negotiation feature set on the same client
Action:: Supply either a content negotiation request context property or a feature, not both. If both are provided, make sure they are set to the same value

OWS-50200: The FastInfosetFeature provided on the client has enabled = {0}, while the service WSDL has enabled = {1}. The client value will override the value read from the WSDL
Category:: WebService
Cause:: The FastInfosetFeature provided on the client is different from that advertised on the service WSDL - client feature will be used as an override
Action:: Make sure that the intent was to override the value advertised in the service WSDL - if not, remove the feature on the client

OWS-50201: Found invalid policy references on WebService endpoint. Please make sure you do not have mulitple or conflicting policy refrerences on your webservice endpoint.
Category:: WebService
Cause:: There is invalid policy set due to conflicting or multiple policy references of same category on given JAXWS endpoint.
Action:: Make sure that there are no multiple or conflicting policy refeences specified on webservcie endpoint.

OWS-50205: Could not create request and response JMSChannel instances required to post JMS messages.
Category:: WebService
Cause:: Internal system error
Action:: Analyze the details of the exception

OWS-50207: Could not open the jar in specified path "{0}"
Category:: WebService
Cause:: The jar is not in the path or the jar format error has occurred
Action:: Check if the jar is in the path or with a wrong path in the Manifest file of current ejb jar which depends on it, then check if the jar has broken

OWS-51001: No TypeGeneratorFactory implementation found for factory {0}.
Category:: WebService
Cause:: You may have specified a wrong factory name, or your Web Service libraries are not properly configured.
Action:: Please ensure that you have specified a valid factory name.

OWS-51500: Unable to open or locate the following file or directory: {0}.
Category:: WebService
Cause:: A file or directory was not found or acessible.
Action:: Ensure that the file or directory name is properly specified and accessible.

OWS-51501: No schema mapping found for class {0}
Category:: WebService
Cause:
Action:

OWS-60002: Could not resolve schema resource for namespace "{0}" at location "{1}"
Category:: WebService
Cause:: Could not resolve the schema from given schemaLocation. This may be caused by network problem or malformed or incorrect schemaLocation URL/URI
Action:

OWS-60003: Serializer initialization failed. Unable to define SDO data types.
Category:: WebService
Cause:: Failed to define SDO data types from the given schema/schemas.
Action:: Ensure that the schema/schemas provided through schemaLocation is/are valid and none of the schemas are conflicting with each other.