BPEL DOM Exceptions ORABPEL 09200 - 09250

BPEL DOM Exceptions ORABPEL 09200 - 09250
DOM Exceptions 09200 - 09250

ORABPEL-09200
severity: 10
type: error
name: Invaild to part type.
description: The \"\" assign part \"{0}\" is invalid, the part should not be null and it should be an instance of org.w3c.Element. Please verify the BPEL source at line number \"{1}\".

ORABPEL-09201
severity: 10
type: error
name: The value is invalid.
description: Error in expression: value is empty at line \"{1}\". The variable : \"{0}\" is null, when applied to document shown below:\n{2}
fix: Please check the BPEL source at line number \"{1}\" and verify the \"from\" variable.

ORABPEL-09202
severity: 10
type: error
name: The value is invalid.
description: Error in expression: value is empty at line \"{1}\". The part : \"{0}\" is null, when applied to document shown below:\n{2}
fix: Please check the BPEL source at line number \"{1}\" and verify the \"from\" part.

ORABPEL-09203
severity: 10
type: error
name: The value is invalid.
description: Error in expression: value is empty at line \"{1}\". The XPath expression : \"{0}\" returns zero node, when applied to document shown below:\n{2}
fix: Please check the BPEL source at line number \"{1}\" and verify the \"from\" part xpath query.

ORABPEL-09204
severity: 10
type: error
name: The from value is invalid.
description: According to BPEL4WS spec 1.1 section 14.3, the value should not be empty.
fix: Please check the BPEL source at line number \"{0}\" and verify the .

ORABPEL-09205
severity: 10
type: error
name: XPath query string returns zero node.
description: According to BPEL4WS spec 1.1 section 14.3, The assign activity part query should not return zero node.
fix: Please check the BPEL source at line number \"{1}\" and verify the part xpath query.

ORABPEL-09206
severity: 10
type: error
name: DOM Element creation failed
description: Error occured while creating DOM element, the reason is {0}.

ORABPEL-09207
severity: 10
type: error
name: The XML data is invalid
description: The XML data is invalid; the reason is \"{0}\".
fix: Please verify xml data.

ORABPEL-09208
severity: 10
type: error
name: Cannot copy object
description: An attempt to copy the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09209
severity: 10
type: error
name: Cannot expand shadow object
description: An attempt to resolve the shadow object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09210
severity: 10
type: error
name: Cannot deep copy object
description: An attempt to deep copy the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09211
severity: 10
type: error
name: Cannot do binary deep copy element
description: An attempt to binary deep copy the element \"{0}\" has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09212
severity: 10
type: error
name: Cannot copy object
description: An attempt to copy the moniker \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09213
severity: 10
type: error
name: Cannot load object from moniker
description: An attempt to deserialize an object from its moniker format has failed. The exception reported is: {0}
fix: The object moniker is corrupt; the moniker may have been edited manually.

ORABPEL-09214
severity: 10
type: error
name: Cannot marshall object
description: An attempt to marshall the object \"{0}\" (class \"{1}\") to XML has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the marshall() method is working properly. Otherwise, the document may have been edited manually.

ORABPEL-09215
severity: 10
type: error
name: Cannot read moniker
description: An attempt to read an object''s moniker from the deserializer stream has failed. The exception reported is: {0}
fix: The object moniker is corrupt; the moniker may have been edited manually.

ORABPEL-09216
severity: 10
type: error
name: Cannot save object
description: An attempt to save the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the save() method is working properly. The save() call is the object''s opportunity to persist itself in some form of external storage.

ORABPEL-09217
severity: 10
type: error
name: Cannot write moniker
description: An attempt to write an object''s moniker into the serializer stream has failed. The exception reported is: {0}

ORABPEL-09218
severity: 10
type: error
name: Couldn''t load the referenced element
description: The shadow node \"{0}\" couldn''t find its referenced read-only element. The XPath to load the referenced element is \"{1}\"
fix: The document is corrupt; it may have been edited manually.

ORABPEL-09219
severity: 10
type: error
name: Cannot save element
description: An attempt to save the element \"{0}\" has failed. Because this element is not a root element and for some reason the scope has reference to this element, scope should have references ONLY to root elements.

ORABPEL-09220
severity: 10
type: error
name: Cannot load element
description: An attempt to load the element \"{0}\" has failed. Because this element is not a root element and for some reason the scope has reference to this element, scope should have references ONLY to root elements.

ORABPEL-09221
severity: 10
type: error
name: Cannot serialize DOM element
description: Failed to serialize the DOM element \"{0}\" to binary format. The exception reported is {1}

ORABPEL-09222
severity: 10
type: error
name: Cannot deserialize DOM element
description: Failed to deserialize the DOM element from binary format, the document id {0}. The exception reported is {1}

ORABPEL-09223
severity: 10
type: error
name: XPath query string returns multiple nodes.
description: According to BPEL4WS spec 1.1 section 14.3, The assign activity part and query {0} should not return multipe nodes.
fix: Please check the BPEL source at line number \"{1}\" and verify the part and xpath query {0}.

ORABPEL-09224
severity: 10
type: error
name: Mismatch Assign
description: Cannot set non-element value to an element based variable
fix: Please check the BPEL source.

ORABPEL-09225
severity: 10
type: error
name: Mismatch Assign
description: Cannot set non-message value to a message based variable
fix: Please check the BPEL source.

<>{ "exception.09226.description", "Cannot use simple-typed variable in "+ "setVariableData(String name, String partOrQuery, Object value) or "+ "setVariableData(String name, String partOrQuery, Object value, boolean clone)" },
ORABPEL-09226
severity: 10
type: error
name: Mismatch Assign
fix: Please check the BPEL source.

ORABPEL-09227
severity: 10
type: error
name: Assign Operation Misuse
description: The from-spec for {2} operation must return either an attribute list or an element list.
fix: Please check the BPEL source at line number \"{1}\" and verify the part and xpath query {0}.

ORABPEL-09228
severity: 10
type: error
name: Assign Operation Misuse
description: The message part \"{2}\" of WSDL variable \"{3}\" is not an XML element; {4} operation cannot be performed.
fix: Please check the BPEL source at line number \"{1}\" and verify the part and xpath query {0}.

<>{ "exception.09229.description", "The to-spec does not yield any data; {1} operation cannot be performed." },
ORABPEL-09229
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09230.description", "The parent of the selection result {1} does not exist or is not an XML element; {2} operation cannot be performed." },
ORABPEL-09230
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09231.description", "The selection result at list entry # {1} does not have a parent node; {2} operation cannot be performed." },
ORABPEL-09231
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09232.description", "The selection result at list entry # {1} is not an XML node; {2} operation cannot be performed." },
ORABPEL-09232
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09233.description", "The selection result at list entry # {1} is not an XML element; {2} operation cannot be performed." },
ORABPEL-09233
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09234.description", "The selection result of {1} is not an XML element; {2} operation cannot be performed." },
ORABPEL-09234
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09240.description", "The element list specified by to-spec used in is NOT contiguous. "},
ORABPEL-09240
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09241.description", "The from-list of is element-based, while the to-list is not element-based."},
ORABPEL-09241
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09242.description", "The from-list of is attribute-based, while the to-list is not attribute-based."},
ORABPEL-09242
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09243.description", "A member of the to-list of does NOT have an element as parent."},
ORABPEL-09243
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09244.description", "A member of the to-list of does NOT have a parent node."},
ORABPEL-09244
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09245.description", "Members of the to-list of do NOT share the same parent node."},
ORABPEL-09245
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09246.description", "Couldn't create the xml stream for document \"{0}\", the reason is: {1}"},
ORABPEL-09246
severity: 10
type: error
name: Failed to create xml stream
fix: Please make sure the document \"{0}\" exists in the document table

<>{ "exception.09247.description", "Couldn't get the blob for document \"{0}\", the reason is: {1}"},
ORABPEL-09247
severity: 10
type: error
name: Failed to get Document Blob
fix: Please make sure the document \"{0}\" exists in the document table

<>{ "exception.09248.description", "Couldn't create document builder \"{0}\", the reason is: {1}"},
ORABPEL-09248
severity: 10
type: error
name: Could not create xdk document builder
fix: Please make sure the document builder \"{0}\" class exists in your classpath

ORABPEL-09249
severity: 10
type: error
name: The XML data is invalid
description: The XML text is invalid {0}, the reason is \"{1}\".
fix: Please verify xml text

ORABPEL-09250
severity: 10
type: error
name: XML Document creation failed
description: Error occured while creating XML Document, the reason is {0}.