Run-time mapping exception in JDBC Scenario

Question

Hello There,
            We are working on a "Communication between IDOC and JDBC" Scenario where in the IDOC is successfully getting called in SAP XI from an SAP R/3 system. But!, when we try to map the IDOC structure with a JDBC Database structure through a manually created XSD, it gives the following run-time mapping exception :
"During the application mapping com/sap/xi/tf/_RequestMapping_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformation"
The following is the XSD that we have created manually for the Target JDBC database table structure which shows the parent-child relationship of the database and is causing the above stated exception :  
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v2004 rel. 4 U (http://www.xmlspy.com) by sekhar (MSS) -->
<!W3C Schema generated by XMLSPY v2004 rel. 4 U (http://www.xmlspy.com)>
<xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="ACCOUNT_GROUP" type="xs:byte"/>
     <xs:element name="AUTHORIZATION_GROUP" type="xs:byte"/>
     <xs:element name="CITY" type="xs:string"/>
     <xs:element name="CITY_CODE" type="xs:short"/>
     <xs:element name="COMPANY_CODE" type="xs:short"/>
     <xs:element name="COUNTRY_CODE" type="xs:byte"/>
     <xs:element name="COUNTRY_KEY" type="xs:byte"/>
     <xs:element name="CREATED_DATE" type="xs:short"/>
     <xs:element name="CUSTOMER_CLASSIFICATION" type="xs:boolean"/>
     <xs:element name="CUSTOMER_NUMBER" type="xs:short"/>
     <xs:element name="DISTRICT" type="xs:string"/>
     <xs:element name="FAX_NUMBER" type="xs:int"/>
     <xs:element name="FIRST_NAME" type="xs:string"/>
     <xs:element name="GROUP_KEY" type="xs:byte"/>
     <xs:element name="HOUSE_NUMBER" type="xs:date"/>
     <xs:element name="INDUSTRY_KEY" type="xs:byte"/>
     <xs:element name="INTIAL_CONTACT" type="xs:byte"/>
     <xs:element name="LAST_NAME" type="xs:string"/>
     <xs:element name="LOCATION_NUMBER" type="xs:string"/>
     <xs:element name="NAME_PERSON" type="xs:string"/>
     <xs:element name="POSTAL_CODE" type="xs:int"/>
     <xs:element name="REGION" type="xs:string"/>
     <xs:element name="REGIONAL_MARKET" type="xs:byte"/>
     <xs:element name="TELEPHONE_NUMBER" type="xs:long"/>
     <xs:element name="VENDOR_ACCOUNT" type="xs:byte"/>
     <xs:element name="resultset">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="row"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="row">
          <xs:complexType>
               <xs:choice maxOccurs="unbounded">
                    <xs:element ref="CUSTOMER_NUMBER"/>
                    <xs:element ref="COUNTRY_KEY"/>
                    <xs:element ref="FIRST_NAME"/>
                    <xs:element ref="LAST_NAME"/>
                    <xs:element ref="LOCATION_NUMBER"/>
                    <xs:element ref="AUTHORIZATION_GROUP"/>
                    <xs:element ref="INDUSTRY_KEY"/>
                    <xs:element ref="GROUP_KEY"/>
                    <xs:element ref="ACCOUNT_GROUP"/>
                    <xs:element ref="CUSTOMER_CLASSIFICATION"/>
                    <xs:element ref="VENDOR_ACCOUNT"/>
                    <xs:element ref="REGIONAL_MARKET"/>
                    <xs:element ref="INTIAL_CONTACT"/>
                    <xs:element ref="COMPANY_CODE"/>
                    <xs:element ref="CREATED_DATE"/>
                    <xs:element ref="NAME_PERSON"/>
                    <xs:element ref="CITY"/>
                    <xs:element ref="CITY_CODE"/>
                    <xs:element ref="COUNTRY_CODE"/>
                    <xs:element ref="DISTRICT"/>
                    <xs:element ref="FAX_NUMBER"/>
                    <xs:element ref="HOUSE_NUMBER"/>
                    <xs:element ref="POSTAL_CODE"/>
                    <xs:element ref="REGION"/>
                    <xs:element ref="TELEPHONE_NUMBER"/>
               </xs:choice>
          </xs:complexType>
     </xs:element>
</xs:schema>
IS THERE ANY OTHER WAY OF ACHIEVING THE ABOVE TASK OF AUTOMATICALLY GENERATING THE REQUIRED DESTINATION STRUCTURE ON THE JDBC TARGET SYSTEM SIDE ?. PLEASE ADVICE ASAP.
REGARDS ......
K. Venkat!.

Answer 1

Try setting the classpath properly. It seems the runtime evironment is unable to find the compiled class files. Nothing else is wrong.
--Anil