I am finding that the initial problem I mentioned anyway, was due to the following missing schema item: Integer EXEC_STATE_COUNTER in the posted sql file on the ODE web site: http://ode.apache.org/war-deployment.data/ode_openjpa_mysql-1.3.2.sql.
When I began searching the web for possible information on 'EXEC_STATE_COUNTER', I ran across the Carbon wso2.org product (http://wso2.org/library/carbon ) and noticed that there is a good deal of Carbon/ODE integration activity these days. Furthermore, I found the Carbon schema posted and noticed that it is actually very similar looking to the ODE schema, but it also seems to have a fix for the missing EXEC_STATE_COUNTER column (among other things). Here is the published trunk of the Carbon schema : https://wso2.org/repos/wso2/trunk/carbon/products/bps/modules/distribution/sql/mysql.sql I tried using this schema to ODE with hibernate on a local MySQL database and it seems to work! Could it be that the schema which is checked into the trunk on the Carbon subversion repository is actually the correct schema to be using for ODE 2 Beta 3, and it simply has yet to be published on the ODE web page? -- View this message in context: http://old.nabble.com/SQL-Exception-attempting-to-substitute-MySQL-for-Derby-on-ODE-tp27772399p28015930.html Sent from the Apache Ode User mailing list archive at Nabble.com.
