[ http://issues.apache.org/jira/browse/JS2-408?page=comments#action_12357830 ]
Ate Douma commented on JS2-408: ------------------------------- It turned out that out tests failed, while Jetspeed itself run (so far) without problems on Derby, because our testcases used a different way to initialize and retrieve a datasource. I've replaced all our custom datasource instantiation for the testcases with a JNDI based datasource, just like we do for the portal itself. Now, all tests (except the portal TestLayout testcase which I excluded) pass again. One specific problem I encountered needs mentioning: Derby doesn't support a UNIQUE constraint on a nullable column (which I find odd). This has been resolved for now in the hardcoded Derby phase2-schema.sql by replacing the UNIQUE constraint on the FRAGMENT.PAGE_ID with only an index. For making Derby the default database deployed with Jetspeed-2, we now only need to resolve where to put it (currently hardcoded in /tmp/productiondb), how to package it, and how to access it. The full path to the db is needed in the datasource config or we must use/set the derby.system.home environment parameter. > Make Derby default database, replace Hypersonic > ----------------------------------------------- > > Key: JS2-408 > URL: http://issues.apache.org/jira/browse/JS2-408 > Project: Jetspeed 2 > Type: Improvement > Components: Dependencies > Versions: 2.0-FINAL > Reporter: David Sean Taylor > Assignee: David Sean Taylor > Fix For: 2.0-FINAL > > Make Derby the default database deployed with Jetspeed-2 replacing Hypersonic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
