Problem in handling CMP bean in jboss3.0.4 with BLOB field i

[tcbkarthi]

hi,

i am using jboss3.0.4 and oracle9i . And i am having a table with a field of BLOB type in which i have stored a xml file as an object (using getBinaryStream() and inputstream etc.. in a general java file)
when i am trying to retrieve the file(object) stored in database through CMP bean, i am getting the following
error in jboss server as follows.


11:00:19,588 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.4/server/
default/deploy/BCTest.jar
11:00:42,150 INFO [STDOUT] Begin of TestblobView
11:00:42,230 ERROR [LogInterceptor] TransactionRolledbackLocalException, causedBy:
java.sql.SQLException: Unable to load to deserialize result: java.io.StreamCorru
ptedException: invalid stream header
at org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil.convertToObject(JDBCUtil.java
:747)


is there any way to solve the above problem?


Note: 1) i have set the following tags in my jbosscmp-jdbc.xml file also.

<cmp-field>
<field-name>xml</field-name>
<column-name>XML</column-name>
<jdbc-type>BLOB</jdbc-type>
<sql-type>BLOB</sql-type>
</cmp-field>

2) since i am storing file that is less than 3 kb in size, i am using oracle thin driver (classes12.jar)


Thanks in advance
karthikeyan

[garyls]

Why don't you make your xml field the Java type java.lang.Object.
This translates into the JDBC type JAVA_OBJECT and the SQL type BLOB via the standardjbosscmp-jdbc.xml configuration file in jboss/server/default/conf.

This worked for me.
Hope it solves your problem

[scoy]

Everything you ever wanted to know (and more) is available in the FAQ at http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=forums/

[scoy]

This will not work in JBoss 3.0.4 onward.

Do not use JAVA_OBJECT unless you know exactly what it is for so that you can provide the support code for it.

See the JDBC doco for more information.

Change JAVA_OBJECT to VARBINARY or LONGVARBINARY if you have used it already. This is fully compatible with previous behaviour, as JBoss was effectively doing this under the covers in releases prior to 3.0.4 anyway.

Steve