001

Specified key does not exist in myParserClass hashmap

This configuration issue should never occur. When transformation has been configured, the requestparsermanager.xml file is used to control the creation of RequestParsers that are used to parse the request to extract information from the request. If this exception occurs, the requested RequestParser type has not been configured in the requestparsermanager.xml file.

002

Could not create specified class

The transformation engine uses Reflection—which creates classes at runtime based off parameters—to create instances of classes with the type specified in a configuration file. If the process of creating a class fails, this exception is raised. This exception means that the class specified in the configuration file TransformationManager.xml or the RequestParser manager could not be instantiated.

003

Could not find the requestParserManager.xml file

The requestparsermanager.xml file must be located in the <TomcatHome>/webapps/<qxtend-web-app>/WEB-INF/conf directory. This error indicates that the file cannot be found.

004

Problem occurred while creating DocumentWrapper

Indicates the XML document being loaded is invalid.

005

Specified key does not exist in myTransformationClasses

Similar exception to 001. However, instead of not having the RequestParser configured, it is the Transformer class that has not been configured in the transformationmanager.xml file.

006

Could not locate the transformationmanager.xml file at the specified location

The transformationrmanager.xml file must be located in the <TomcatHome>/webapps/<qxtend-web-app>/WEB-INF/conf directory. This error indicates that the file cannot be found.

007

No transformer node in transformationmanager.xml

The transformationmanager.xml file requires a predefined structure. As part of that structure it requires a node named transformer. If that node cannot be found in the correct place, this exception is thrown.

008

Envelope header is null

When processing transformations it is required that the request contains a SOAP envelope, this error is thrown if a request does not contain a SOAP envelope.

009

Problem getting request header and body

When processing Transformations the engine split the SOAP message into two parts—the header and the body. This exception indicates that the request could not be split.

010

Problem occurred creating transformer

Transformation uses a shared library for executing the transformations. The first step is to obtain a Transformer class from a TransformerFactory class. This exception is thrown when the creation of the Transformer class fails.

011

Error occurred during transformation

An unhandled error occurred while the transformer was processing the XSLT transformation.

012

Problem occurred while setting the response header and body

While building the response message—which is a SOAP message with a header and a body—an unhandled error occurred.

013

No child node of root node present

If the request XML being transformed does not have a root node (single node with no parent), this exception is thrown.

014

Problem getting parser from requestParserManager

The Request Parser Manager controls access to all request parser instances. This exception is raised when a request parser is requested from the Manager, and it cannot return one.

015

Could not find the queue configuration file

Indicates that for a specific queue the queueconfig.xml file could not be found.

018

No requestParsers node present in XML

The requestparsermanager.xml file requires a predefined structure. As part of that structure it requires a node named requestParsers. If that node cannot be found in the correct place, this exception is thrown.

019

No matching mapping specification found

The valid mapping specifications are defined in transformationmanager.xml. This exception indicates that for the combination of documentStandard, documentType, documentVersion, and receiver that no mapping specification could be located to use to transform the message. Change the configuration in transformationmanager.xml to ensure that there is a mapping specification defined.