Hi Clovis,
I'm quite sure that nothing changed at mapping since 0.9.5.2 but I realy
don't know what happend before that time. According to the stacktrace I
also think that this is a problem with the mapping.
I suggest to comment out all classes except a very simple one. If you
can initialize JDOManager with the simple mapping you can add your old
mappings step by step to find where it fails.
To run the Castor test suite you need to execute the script
src/tests/jdo/sapdb.sql
and edit
src/tests/jdo/sapdb.xml
to reflect you configuration. After building castor by
build clean
build tests
you can run test suite with the command
test castor.sapdb
You can also execute a specific test by e.g.
test castor.sapdb.TC01
More information on excuting the test suite can be found under
http://castor.codehaus.org/test-framework.html
I'm leaving office now (it's 8:00 here in germany). As you may need to
work a little more in brazil you can connact me at IRC. This will also
reduce time for response compared to mail. Hope to see you at:
irc://irc.codehaus.org/castor
Regards
Ralf
clovis_wichoski schrieb:
Hi Ralf,
Changing to Driver now I get follow exception:
java.lang.ClassCastException:
org.exolab.castor.mapping.handlers.EnumFieldHandler
at
org.exolab.castor.jdo.engine.SQLEngine$FieldInfo.(SQLEngine.java:1618)
at org.exolab.castor.jdo.engine.SQLEngine.(SQLEngine.java:280)
at
org.exolab.castor.jdo.engine.BaseFactory.getPersistence(BaseFactory.java:84)
at org.exolab.castor.persist.ClassMolder.resolve(ClassMolder.java:532)
at org.exolab.castor.persist.LockEngine.(LockEngine.java:164)
at
org.exolab.castor.persist.PersistenceEngineFactory.createEngine(PersistenceEngineFactory.java:80)
at
org.exolab.castor.jdo.engine.DatabaseRegistry.(DatabaseRegistry.java:727)
at
org.exolab.castor.jdo.engine.DatabaseRegistry.(DatabaseRegistry.java:690)
at
org.exolab.castor.jdo.engine.DatabaseRegistry.initFromDriver(DatabaseRegistry.java:449)
at
org.exolab.castor.jdo.engine.DatabaseRegistry.initDatabase(DatabaseRegistry.java:274)
at
org.exolab.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:200)
at
org.exolab.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:153)
at
org.exolab.castor.jdo.JDOManager.loadConfiguration(JDOManager.java:289)
at
org.exolab.castor.jdo.JDOManager.loadConfiguration(JDOManager.java:322)
...
I think that this is in mapping, mapping has changed too?
Having said that I think that nowone run the test cases for sapdb for a
long time :-( . The problem with sapdb is that none of the commiters
have it installed yet. We would very much apreciate if you could help
use with this task ;-) .
sure I will do. only I need to know where to start for tests.
Thanks Ralf
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
