DataSource issue

Hello,

I am faced to this issue below :

java.lang.ClassCastException: org.apache.commons.collections.map.LinkedMap cannot be cast to java.util.List
at com.isomorphic.datasource.DataSource.getOperationBindings(DataSource.java:766)
at com.isomorphic.sql.SQLDataSource.init(SQLDataSource.java:236)
at com.isomorphic.datasource.DataSource.initialize(DataSource.java:486)
at com.isomorphic.datasource.BasicDataSource.fromConfig(BasicDataSource.java:177)
at com.isomorphic.datasource.DataSource.fromConfig(DataSource.java:471)
at com.isomorphic.datasource.FileSystemDSRepo.loadDS(FileSystemDSRepo.java:110)
at com.isomorphic.datasource.DataSource.forName(DataSource.java:230)
at com.isomorphic.datasource.DataSource.forName(DataSource.java:222)
at com.isomorphic.datasource.DataSource.forName(DataSource.java:211)
at com.isomorphic.datasource.PoolableDataSourceFactory.makeUnpooledObject(PoolableDataSourceFactory.java:130)
at com.isomorphic.datasource.PoolableDataSourceFactory.makeObject(PoolableDataSourceFactory.java:138)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1179)
at com.isomorphic.pool.ISCKeyedObjectPool.borrowObject(ISCKeyedObjectPool.java:106)
at com.isomorphic.pool.PoolManager.borrowObject(PoolManager.java:84)
at com.isomorphic.datasource.DataSourceManager.getDataSource(DataSourceManager.java:135)
at com.isomorphic.datasource.DataSourceManager.getDataSource(DataSourceManager.java:86)
at com.isomorphic.datasource.DataSourceManager.getDataSource(DataSourceManager.java:82)
at com.isomorphic.datasource.DataSourceManager.get(DataSourceManager.java:167)


For your information, we have migrated GWT from 2.5 to 2.7.0 because I thought you don't depend on GWT .


Could you help me, please?

Best regards,

Zahir,




Be sure your post includes:

1. the *complete* SmartGWT or SmartClient version from the lower left-hand corner of the Developer Console (see FAQ for how to open Developer Console), for example, \"v8.2p_2012-04-18/PowerEdition Deployment\"

2. browser(s) and version(s) involved

3. for a server-side problem, the *complete* logs generated during processing of the failing request (do *not* trim to just the error message)

4. for any problem processing a server response, the actual response as shown in the RPC tab in the Developer Console

5. if there is a JavaScript error, the stack trace logged in the Developer Console (see FAQ)

6. sample code if applicable

Posts with incomplete information are much more likely to be ignored.