You're welcome. I'll take a look at the forms and survey plugins when time permits. Thanks.

Note that both plugins forms and survey perform a test on the db type during their processing.
To have full hsqldb support, we also have to patch these plugins.
I'll open related issues.

Committed in trunk

I've added unit tests

Thanks again for the patches !

You're welcome. I'm proud of the contribution I made since I'm a Java beginner.

Anyway, I still need help with using HSQLDB for the repository. I tried using BundleDbPersistenceManager class as a persistence manager for HSQLDB, but I kept getting NODE_ID and NODE_ID_HI errors.

I'll mark the issue as resolved as soon as your patch are committed.
I'll write some unit tests too.

By the way, thanks for the patches.

I think the runtime works fine with HSQLDB even though I didn't perform unit tests. Can this issue be closed as resolved? I hope the patches make it into the release.

Attached are more patches related to using HSQLDB for group/profile management

I don't know how to perform the test yet. Instead, I created an empty HSQL database, HSQLDB scripts and a config file for others to perform the test.

Seems nice. If you want the work to be complete (for the Runtime part), you can take a look at the unit tests located in the test folder of the Runtime project (DerbyXxxTestCase).
The tests should be simple enough to adapt, the only differences between the DBMS are:

• the JDBC connection info in the test/environments/configs/config_xxx.xml configuration file
• some SQL scripts used by the tests in the test/environments/scripts/jdbc-xxx directory

Setting up an environment to run the tests is complex, but the tests should run fine if the SQL scripts can be run in a HSQLDB database.

Thanks, Nicolas
The patch seems to get rid of the "statement not in batch mode" error.
At this moment, I don't get any more error related to using HSQLDB.