Hello all! Regarding the issues between JBoss and SAP DB:
Mapping of JAVA_OBJECT: ----------------------- The mapping that should be used is: <mapping> <java-type>java.lang.Object</java-type> <jdbc-type>JAVA_OBJECT</jdbc-type> <sql-type>LONG BYTE</sql-type> </mapping> In the JBoss there is clearly handling that serializes/deserializes Objects into the fields, so there is no need for this in the driver. If you get errors like "Cannot put ASCII data into this LONG column." then please check the type of the offending column in the schema - it must not be LONG ASCII or LONG UNICODE, or any other *character* type (CHAR, VARCHAR, CHAR UNICODE, VARCHAR UNICODE). Keep this also in mind if you let JBoss operate using CMP on schemas you have defined by yourself. Configuration: -------------- For my testing purposes, the configuration files provided with JBoss itself, and the file I posted some time ago for the XA data source implementation worked, but you may of course correct the file if there is something that does not work like you expect because it seems to work for other databases and JDBC drivers. If you have problems achieving a specific setup in general, please use the JBoss forums to get help for your problems. Memory Leaks: ------------- Im curious to hear more about this. We had a big one a long time ago, but this is gone, so I'm really curious to hear about that, and possibly the circumstance where it occurs. The driver should not have a memory leak, if it still has one, this should be fixed ... Regards Alexander Schr�der SAP Labs Berlin
sapdb-xa-service.xml
Description: Binary data
