What JDBC/SQL mappings are you using?
The datasource-mapping is set to Oracle8.
For the field we defined as Timestamp we use the default values for the field we use as Password (that is a byte) we force the values on jbosscmp-jdbc:
We are using jboss 3.0.3
You are using a very old version of JBoss 3.0.
In fact, 3.0.4 had significant fixes to the handling of binary data.
Also, there are now Oracle 9i datasource mappings with proper support for the TimeStamp datatype (which does not exist in Oracle 8).
Using JBoss 3.0.4 or later, VABINARY/RAW should work fine for your password field.
Hi, now I'm using JBoss 3.2.2RC2 and I changed the mapping for Oracle9i.
If I don't change the type of the column on the database from DATE to TIMESTAMP the problem remains...if I change it works with no problem.
I tried to force the configuration on the jbosscmp-jdbc to:
but jboss throws an exception when it tries to persist the data!!
I still don't know what's happening here!! But it's really strange!
What's the exception?
Please show the full stack trace.
Is it possible that you created the table with an SQL type of TIMESTAMP initially?
We don't have any field as TIMESTAMP. We always used DATE.
I tried to make a change, I redefined the field as VARCHAR2 and in my Entity bean I put a method that converts the byte array to a two digits hexadecimal.
It's strange but the problem is still there! I think that it can be a situation where my entity bean (or my session bean maybe) throws some kind of exception that I catch in any part of the code but doesn't show the stack trace !
I will provide you the stack trace asap!!
Thanks for your help!!
I attached the piece of log messages of my server.log where you can find the stack trace.