82 SOA-00000 to SOA-00043

SOA-00000: Malformed WS Binding port. Missing # between namespace URI and service/port names.

Cause: Malformed webservice binding component port configuration

Action: Correct the port attribute for ws binding component in the composite configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00001: Malformed WS Binding port. Missing '/' between service and port name

Cause: Malformed webservice binding component port configuration

Action: Correct the port attribute for ws binding component in the composite configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00002: No service name found.

Cause: No service name found in webservice binding component configuration

Action: Add the service name attribute for ws binding component in the composite configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00003: Number of SOAP body elements and parts do not match in operation: {0}

Cause: Malformed SOAP request. Number of Parts in the soap body does not match with WSDL definition.

Action: Correct the SOAP message.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00004: Response message does not match output defined in the WSDL: output of operation "{0}" is null, but response message contains payload.

Cause: SOAP response does not match WSDL definition.

Action: Correct the SOAP message.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00007: Unable to find service: {0}

Cause: Specified service is not found in the WSDL.

Action: Either correct the wsdl or the service name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00008: Unable to find port: {0}

Cause: Specified port is not found in the WSDL.

Action: Either correct the wsdl or the port name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00009: Unable to find operation: {0}

Cause: Specified operation is not found in the WSDL.

Action: Either correct the wsdl or the operation name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00010: Error in create Documentbuilder.

Cause: Failure to create a new DocumentBuilder class.

Action: Server configuration may have to be corrected.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00011: Problem in parsing componentType {0}.

Cause: Problem in parsing component type file.

Action: Correct the component type file configuraiton.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00012: Request message does not match input defined in the WSDL: input of operation "{0}" is null, but request message contains payload.

Cause: Request message does not match input defined in the WSDL. Input is not defined, but there is an input payload.

Action: Correct the wsdl.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00013: Malformed WSDL Interface attribute. Missing # between namespace URI and interface name.

Cause: Malformed WSDL Interface attribute. Missing # between namespace URI and interface name.

Action: Add # between namespace URI and interface name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00014: No interface name found.

Cause: Specified interface not found in the WSDL definition.

Action: Correct the input wsdl or interface name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00015: Error in getting XML input stream: {0}

Cause: Failure in processing XML document.

Action: Make sure the xml input is valid.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00016: Failed to concatanate the following 2 urls: home= "{0}" and relative="{1}".

Cause: Failure in creating urls from the given home url and relative url.

Action: Correct the home or the relative urls.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00018: Failed to find a component type file: compositeDN = "{0}" and component="{1}".

Cause: Failed to find component type file.

Action: Correct the component type file name.

Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00019: Missing "{0}" delimeter

Cause: Missing a delimiter.

Action: Add the missing delimiter.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00020: Unable to instantiate composite class loader due to exception {0}

Cause: Failure instantiating composite classloader.

Action: Check the exception for detailed messages.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00021: No reference "{0}" defined for service "{1}"

Cause: No Reference defined for the given service.

Action: Correct the composite configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00022: Error Loading XML Schema {0}

Cause: Failure to find the specified schema.

Action: Correct the schema location referenced.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00023: Incorrect config object type.

Cause: Incorrect Object Configuration type.

Action: Correct the configuration for the object.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00025: Unable to convert to SDO: {0}

Cause: Failed to convert xml input to SDO object.

Action: Check the exception message. You may have to correct the schema definition or configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00026: Error converting SDO to XML: {0}

Cause: Failure in converting sdo objects to xml messages.

Action: Check the exception message. You may have to correct the schema definition or configration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00027: Cannot remove property "{0}" that was defined in the componentType.

Cause: Unable to remove the property defined in the component type file.

Action: Correct the component type configuraiton file.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00028: Invalid value for mode. It should be either active or retired mode.

Cause: Invalid mode specified in the composite

Action: Provide valid mode such as active or retired.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00029: Invalid value for mode. It should be either on or off state.

Cause: Invalid state specified in the composite

Action: Provide valid state such as on or off.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00030: Could not use reflection to get properties from the bean of class: {0}. {1}

Cause: Failure in retrieving bean properties

Action: Check exception message for details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00031: Binding Type {0} is unknown.

Cause: The type of binding is undefined.

Action: Please check document for valid binding types supported.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00033: An MBean of name "{0}" doesnt exist. Unable to update its state.

Cause: Specified mbean does not exist.

Action: Correct the mbean name used.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00034: Unable to load the "{0}" file from "{1}" directory.

Cause: Failed to load the file using mdm configuration.

Action: Correct the MDM configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00035: Variable "{0}" not defined in mdm-url-resolver.xml.

Cause: The variable is not defined in the mdm configuration file.

Action: Correct the mdm configration file.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00036: mdm-url-resolver.xml not loaded

Cause: MDM url resolver is not loaded.

Action: Check the server configuration for MDM setup.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00037: Malformed Java Binding port. Missing # between namespace URI and service/port names.

Cause: Port type in binding component is invalid.

Action: Check the port type attribute and correct the syntax used.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00038: Malformed Java Binding port. Missing name of the portType

Cause: Port type in binding component is invalid.

Action: Check the port type attribute and correct the syntax used.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00039: Invalid composite element name "{0}". Element names in a composite have to be unique.

Cause: Invalid composite file.

Action: Correct the element name used for the composite.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00040: Unable to convert sdo to xml, element name not found.

Cause: Failed to convert sdo objects to xml messages

Action: Check the schema definition referenced from the wsdl.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00043: Unable to convert sdo to xml, missing sdo metadata.

Cause: Failed to convert sdo objects to xml messages. Metadata for the conversion is not found.

Action: Check the schema definition referenced from the wsdl.

Level: 1

Type: ERROR

Impact: Requests/Responses