ParseTDS error using XSQL demos

Question

I recently installed the Oracle XSQL servlet engine. When I try one of the demos that make use of object views, I get the following error message:
<?xml version="1.0" encoding="UTF-8" ?>
<ERROR>oracle.xml.sql.OracleXMLSQLException: Fout bij ontleden typedescriptor: parseTDS</ERROR>
There is some Dutch in this, which is a bit odd, but the text "Fout bij ontleden typedescriptor" means "Error parsing type descriptor". What could be wrong?

Answer 1

I am using an Oracle 8.1.6 server. On the machine that runs the XSQL servlet, I have an 8.0.5 Net8 connection, but I assume that this is not important, since this should not be used by the Oracle JDBC driver. All examples work as long as the objecty views are not used.
I don't know how this parser works internally, but I think it might have something to do with the absence of some of the field names in the query result.
Here's what I mean: when I try the insurance demo, and select example three, I get the correct result. When I execute the associated query in SQL*Plus, I get the following result:
SQL> select c.claimpolicy.primaryinsured as Customer
2 from insurance_claim_view c
3 where c.claimpolicy.primaryinsured.homeaddress.state = 'CA'
4 ;
CUSTOMER(CUSTOMERID, FIRSTNAME, LASTNAME, HOMEADDRESS(STREET, CITY, STATE, ZIP))
POLICYHOLDER_T(1044, 'Paul', 'Astoria', ADDRESS_T('123 Cherry Lane', 'SF', 'CA', 94132))
POLICYHOLDER_T(1044, 'Paul', 'Astoria', ADDRESS_T('123 Cherry Lane', 'SF', 'CA', 94132))
POLICYHOLDER_T(1045, 'Martina', 'Boyle', ADDRESS_T('55 Belden Place', 'SF', 'CA', 94102))
POLICYHOLDER_T(1045, 'Martina', 'Boyle', ADDRESS_T('55 Belden Place', 'SF', 'CA', 94102))
As you can see, all field names, which serve as tags in the XML result, are present. From this result, you can derive that there is a sub-object HOME_ADDRESS consisting of the fields STREET, CITY, STATE and ZIP.
For insurance example four, the result in SQL*Plus looks like this:
SQL> select v.claimpolicy.primaryinsured.homeaddress as address,
2 v.settlements
3 from insurance_claim_view v
4 ;
ADDRESS(STREET, CITY, STATE, ZIP)
SETTLEMENTS(PAYDATE, AMOUNT, APPROVER)
ADDRESS_T('123 Cherry Lane', 'SF', 'CA', 94132)
SETTLEMENTS_T(PAYMENT('05-JAN-99', 7600, 'JCOX'))
ADDRESS_T('123 Cherry Lane', 'SF', 'CA', 94132)
SETTLEMENTS_T(PAYMENT('15-MAR-98', 1800, 'MFOX'), PAYMENT('23-MAR-98', 7800, 'ULOWE'))
ADDRESS_T('55 Belden Place', 'SF', 'CA', 94102)
SETTLEMENTS_T(PAYMENT('01-JUL-97', 1500, 'JCOX'))
ADDRESS_T('55 Belden Place', 'SF', 'CA', 94102)
SETTLEMENTS_T(PAYMENT('05-JAN-99', 7600, 'JCOX'))
The result contains a reference to the object PAYMENT, but the definition of this object cannot be derived from the column names.
If the parser indeed uses these column names to derive an object structure, this may be the cause, but the question is: what went wrong during the installation that caused this problem?