>> For that reason, I think we should consider replacing Derby with another embedded database for OFBiz’s out-of-the-box/demo setup.
Hello All, I agree that we should consider replacing the Derby database with another embedded database. I also agree that H2 appears to be the best option at the current time. I went ahead and replaced Apache Derby in my OFBiz trunk codebase with the H2 database. After the changes, I tested the ofbiz code base on H2 db by placing an Order, completing it, and also created a new customer. These operations are working fine for me. I have pushed the H2-specific modified code to a branch in my forked repository. Please take a look at the code below and let me know your thoughts. https://github.com/ashishvijaywargiya/ofbiz-framework/tree/default-h2-db-support-ofbiz-trunk If there are no objections, I will create a PR sometime next week to merge the code into the OFBiz project. Thank you. -- Kind Regards, Ashish Vijaywargiya Vice President of Operations *HotWax Systems* *Enterprise open source experts* http://www.hotwaxsystems.com On Thu, May 7, 2026 at 1:20 PM Jacopo Cappellato < [email protected]> wrote: > Hi all, > > Since Apache Derby is now retired, it will no longer receive updates for > bug fixes or security issues. > For that reason, I think we should consider replacing Derby with another > embedded database for OFBiz’s out-of-the-box/demo setup. > > Would anyone be willing to volunteer in either of these areas? > * researching and suggesting suitable alternative products that would fit > OFBiz well; > * implementing the switch once we agree on a direction. > > As an alternative, we could also consider no longer shipping a bundled > database at all, and instead relying on Docker images to make demo > instances easy to start. > That would be a more significant change for users, so perhaps not something > for immediate adoption, but I think it is probably the right direction to > keep in mind for the future. > > Thoughts? > > Best, > Jacopo > > > On Thu, Dec 4, 2025 at 9:43 AM Jacques Le Roux < > [email protected]> > wrote: > > > Hi, > > > > FYI, not a problem IMO. It works as is. > > > > Jacques > > > > > > > > -------- Message transféré -------- > > Sujet : Apache Derby is now retired > > Date : Wed, 3 Dec 2025 09:38:15 -0800 > > De : Richard Hillegas <[email protected]> > > Répondre à : [email protected] > > Pour : [email protected] > > > > > > > > The DB PMC announces the retirement of its Derby sub-project, due to > > prolonged low activity. Derby is a small-footprint, pure-Java relational > > database. Derby runs embedded in a local application as well as > > client-server over a network. Databases can live on disk or in memory. > > Existing, > > official versions support JVMs from Java 1.3 up through Java 21. The > > development mainline builds and tests cleanly on Java 25. > > > > The project's resources remain available in a read-only state. This > > includes the website (https://db.apache.org/derby/), mailing lists, wiki > > (https://cwiki.apache.org/confluence/display/DERBY/FrontPage), > Subversion > > repository, and JIRA bug tracker. Official distributions remain available > > on > > an as-is basis at https://db.apache.org/derby/derby_downloads.html. > > >
