BPEL XML Exceptions ORABPEL 09000 - 09021

BPEL XML Exceptions ORABPEL 09000 - 09021
XML Exceptions 09000 - 09021

ORABPEL-09000
severity: 10
type: error
name: Cannot copy class files
description: Cannot copy generated XML schema classes from \"{0}\" to \"{1}\". The exception reported is: {2}

ORABPEL-09001
severity: 10
type: error
name: Cannot copy source files
description: Cannot copy generated XML schema java source files from \"{0}\" to \"{1}\". The exception reported is: {2}

ORABPEL-09002
severity: 10
type: error
name: File process error
description: Error processing file \"{0}\", because \"{1}\".
fix: Please ensure that the input \"{0}\" is available and valid.

ORABPEL-09003
severity: 10
type: error
name: Failed to normalize name
description: Failed to normalize the name \"{0}\".
fix: Please ensure that the name \"{0}\" is available and valid.

ORABPEL-09004
severity: 10
type: error
name: Failed to marshall object
description: Failed to marshall the class \"{0}\" to XML. The exception reported is: {1}

ORABPEL-09005
severity: 10
type: error
name: Failed to unmarshall object
description: Failed to unmarshall the class \"{0}\" from XML. The exception reported is: {1}

ORABPEL-09006
severity: 10
type: error
name: Incompatible schema object version
description: The XML schema class \"{0}\" has been compiled with an older version of SCHEMAC; the BPEL process domain you have deployed the class to cannot use the helper classes generated for this class.
fix: Please recompile your XML schema using the SCHEMAC tool bundled with the current process domain.

ORABPEL-09007
severity: 10
type: error
name: Error while instantiating marshaller
description: An error has occurred while attempting to instantiate the XML marshaller/unmarshaller class \"{0}\"; the exception reported is: {1}

ORABPEL-09008
severity: 10
type: error
name: Wrong marshaller interface
description: The class \"{0}\" does not implement the com.collaxa.cube.engine.xml.IMarshaller interface. All XML marshallers used in the BPEL domain must implement this interface.

ORABPEL-09009
severity: 10
type: error
name: Wrong schema registry interface
description: The class \"{0}\" (for the runtime schema registry) does not implement the ISchemaRegistry interface. All schema registries used by the runtime must implement this interface.

ORABPEL-09010
severity: 10
type: error
name: Error while creating schema registry
description: An error has occurred while attempting to instantiate the class \"{0}\" as the runtime schema registry. The exception reported is: {1}

ORABPEL-09011
severity: 10
type: error
name: Unknown schema registry classname
description: The classname for the runtime schema registry has not been specified.

ORABPEL-09012
severity: 10
type: error
name: Unmarshaller not found
description: The XML unmarshaller for class \"{0}\" cannot be found. Every scope type used in a process must provide an XML unmarshaller.
fix: Please check that an unmarshaller for the class \"{0}\" has been registered properly with the process domain during process initialization.

ORABPEL-09013
severity: 10
type: error
name: SAX exception
description: SAX exception occurred when parsing \"{0}\", because \"{1}\".
fix: Please ensure that the input \"{0}\" is available and valid.

ORABPEL-09014
severity: 10
type: error
name: Cannot resolve type
description: Type \"{1}\" of \"{0}\" cannot be resolved.
fix: Please ensure that the input XML file is syntactically correct.

ORABPEL-09015
severity: 10
type: error
name: Class to QName mapping failure
description: TypeManager could not map the class name \"{0}\" to QName because \"{1}\"
fix: Please ensure the XML schema type \"{0}\" is valid.

ORABPEL-09016
severity: 10
type: error
name: Class name to QName mapping failure
description: TypeManager could not map the class name \"{0}\" to QName because \"{1}\"
fix: Please ensure the XML schema type \"{0}\" is valid.

ORABPEL-09017
severity: 10
type: error
name: QName to java class mapping failure
description: TypeManager could not map the QName \"{0}\" to java class because \"{1}\"
fix: Please ensure the XML schema type \"{0}\" is valid.

ORABPEL-09018
severity: 10
type: error
name: Failed to create XML parser
description: Failed to create XML parser.
fix: This error might be related to CLASSPATH configuration.

ORABPEL-09019
severity: 10
type: error
name: WSDL or jbpel file not valid
description: Error processing file \"{0}\", because {1}.
fix: Please ensure that the input WSDL or jbpel file \"{0}\" is available and valid.

ORABPEL-09020
severity: 10
type: error
name: Missing argument
description: Missing expected filename/classname argument.
fix: Please type \"{0} -help\" for more information.

ORABPEL-09021
severity: 10
type: error
name: XML Schema \"include\" is not currently supported
description: XSD file \"{0}\" is trying to include XSD file \"{1}\". Schemac does not currently support \"include\".
fix: Schemac does support \"import\". You can change \"{0}\" to use \"import\", or you can physically include \"{1}\" in \"{0}\".