XMLType inputstream on OCI client

Question

Hi all, I have a problem using XMLType.createXML in java to create a XMLType to use as parameter in a stored procedure using OCI client (it works with thin client).
my environment (sorry if I missed something!):
Oracle db 11.1 on server, Java 1.6 and OCI client 11.1 on Windows on client.
In my Eclipse project I included the following jars:
\jdbc\lib\ojdbc6.jar
\jlib\orai18n.jar
\RDBMS\jlib\xdb.jar
\LIB\xmlparserv2.jar
the java code snippet for calling the stored procedure using the input stream:
public String putgetXMLInputStream(File testFile) throws SQLException, FileNotFoundException, UnsupportedEncodingException
     // create the input stream from the file containing XML
     InputStream br = new BufferedInputStream(new FileInputStream(testFile));      
// this statement was tested with no value for "kind" parameter and with these two value too
     // "oracle.xml.parser.XMLDocument.THICK"
     // "oracle.xml.parser.XMLDocument.THIN"
     XMLType xmlDoc = XMLType.createXML(connection, br);
     // set the statement
     CallableStatement cs;
     cs = connection.prepareCall("{?=call MYPACKAGE.TESTUPLOAD(?)}");
cs.registerOutParameter(1, OracleTypes.VARCHAR);           
     cs.setObject(2, xmlDoc);
// execute the statement
     cs.execute();
     // return the string
     return cs.getString(1);
same code with string:
public String putgetXMLString(File testFile) throws SQLException, FileNotFoundException, UnsupportedEncodingException, IOException
     StringBuilder contents = new StringBuilder();
     try {
     //use buffering, reading one line at a time
     //FileReader always assumes default encoding is OK!
     BufferedReader input = new BufferedReader(new FileReader(aFile));
     try {
          String line = null; //not declared within while loop
          * readLine is a bit quirky :
          * it returns the content of a line MINUS the newline.
          * it returns null only for the END of the stream.
          * it returns an empty String if two newlines appear in a row.
          while (( line = input.readLine()) != null){
          contents.append(line);
          contents.append(System.getProperty("line.separator"));
     } finally {
     input.close();
     XMLType xmlDoc = XMLType.createXML(connection, contents.toString());      
     // set the statement
     CallableStatement cs;
     cs = connection.prepareCall("{?=call MYPACKAGE.TESTUPLOAD(?)}");
cs.registerOutParameter(1, OracleTypes.VARCHAR);           
     cs.setObject(2, xmlDoc);
// execute the statement
     cs.execute();
     // return the string
     return cs.getString(1);
the java code snippet for establish the database connection (I know that with java 1.6 the registerDriver is not
required, I both tested with and without driver registering and it works in the same way):
// connection string: comment as required
// connection string for thin client
// String connectionString = "jdbc:oracle:thin:@mydbserver:1521:mydb";
// connection string for oci
String connectionString = "jdbc:oracle:oci8:@mydbserver:1521:mydb";
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn =DriverManager.getConnection( connectionString, "john", "tiger");
DatabaseMetaData meta = conn.getMetaData();
System.out.println("Driver JDBC: " + meta.getDriverVersion());
The PL/SQL called by java:
FUNCTION TESTUPLOAD (pDoc IN XMLTYPE) RETURN VARCHAR2 IS
msgout VARCHAR2(24000);
doc DBMS_XMLDOM.DOMDocument;
rootnode DBMS_XMLDOM.DOMNode;
fchild DBMS_XMLDOM.DOMNode;
attr1 VARCHAR2(20);
ns VARCHAR2(200);
BEGIN
ns := 'xmlns="http://www.myweb.it/static/xml/def/0.6/ns1.html" xmlns:si="http://www.myweb.it/static/xml/def/0.6/si.html"';
doc := DBMS_XMLDOM.newDOMDocument(pDoc);
rootnode := dbms_xmldom.makeNode(doc);
fchild := DBMS_XMLDOM.GETFIRSTCHILD(rootnode);
-- dom text
DBMS_XMLDOM.WRITETOBUFFER(rootnode, msgout);
-- attribute value
dbms_xslprocessor.valueOf(rootnode,'/DOC/@TYPENO',attr1, ns );
-- node name of rootnode first child
return '(' || attr2 || ' - ' || DBMS_XMLDOM.GETNODENAME(fchild) || ') ' || msgout;
END TESTUPLOAD;
Thus, the expected result is a returned varchar2 containing the value of the attribute as per XPath, the name of first child node
and the whole text of dom.
This work as expected connecting via OCI and Thin client if I create the XML starting from a string, and only with Thin client if
I adopt the input stream approach. If I use the input stream with OCI client, no error message is displayed, and no value are provided
for attribute or fchild name, but the dom text is returned.
I made test with different charset encoding for the original file (UTF-8, ISO-8859-1, with endofline in windows and linux style).
What I noticed is that in case of string and input stream with Thin client some kind of parsing occours: the returned text show some
special characters (i.e. double quote) replaced by html entity and the charset encoding in <?xml tag replaced with ISO-8859-1, more over
the returned xml is well indented.
I'm sure that I'm missing something :-)
Any hints?
TIA
GB
Edited by: user12844059 on 7-mag-2010 6.54

Answer 1

visit the javasoft.com (sun site) for tutorials and training on all of the technologies you mentioned.
after understanding them, then review the oracle java roadmap found on technet.oracle.com --> technologies --> java to get an oracle perspective.
then ask the oracle technology specific questions you have.