Hi Charles,
we've encounter same problem as you. Its caused by different type
definitions in java, jdbc driver, castor and sql.
Have a look on this example:
<field name="startDate" type="date">
<sql name="START_DATE"/>
<bind-xml name="startDate" node="element"/>
</field>
wich leads to a ClassCastException in case that column START_DATE from
sql type Timestamp. You have additional define the sql type in mapping
like this:
<field name="startDate" type="date">
<sql name="START_DATE" type="timestamp"/>
<bind-xml name="startDate" node="element"/>
</field>
> To sum up, can we now assume that PoolMan is obsolete
> and cannot be configured with JSDK 1.5, Castor 0.9.7 -- in which
> case, the online Castor documentation should reflect this limitation?
You are right, poolman is obsolete. No support, no update and a lot of
bugs such ConcurrentModificationException after DataBase#commit(). Try
as substitution Apache DBCP. Its easy to use:
<database name="XXXXXX" engine="sapdb" >
<data-source class-name="org.apache.commons.dbcp.BasicDataSource">
<param name="url" value="jdbc:sapdb://xxx.xxx.xxx.xxx/MC4"/>
<param name="driver-class-name" value="com.sap.dbtech.jdbc.DriverSapDB" />
<param name="username" value="XXXXXXXXX"/>
<param name="password" value="xxxx"/>
<param name="initial-size" value="10" />
<param name="max-active" value="20" />
</data-source>
</database>
Change your JDO conf as above. Migration to Apache DBCP takes 1-2 hours
and works fine.
Regards
Andre Teubner
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
