Subject: XML shredding and thick JDBC driver
Hi,
I'm a Web Services developer. I'm looking into XML shredding (structured/object-relational storage), and I'm wondering what it means when the XML DB Developer's Guide says:
----------------------------------------------------
"Use the thick JDBC driver with schema-based XMLType values stored object-relationally. (You can use either the thin or the thick driver with CLOB storage of XMLType values.)"
----------------------------------------------------
Does this mean that the shredding is done in the client, not in the database?
Is the thick JDBC driver only necessary between the Java layer and the database, or do the Web Service _customers_ need the thick driver? If the former, it's an option for us (as we have control over this part of the system). If the latter, it's a no-go (we can't tell the customers what kind of driver to use).
I'm a Web Services developer. I'm looking into XML shredding (structured/object-relational storage), and I'm wondering what it means when the XML DB Developer's Guide says:
----------------------------------------------------
"Use the thick JDBC driver with schema-based XMLType values stored object-relationally. (You can use either the thin or the thick driver with CLOB storage of XMLType values.)"
----------------------------------------------------
Does this mean that the shredding is done in the client, not in the database?
Is the thick JDBC driver only necessary between the Java layer and the database, or do the Web Service _customers_ need the thick driver? If the former, it's an option for us (as we have control over this part of the system). If the latter, it's a no-go (we can't tell the customers what kind of driver to use).
0