Hi ? (no name given),
I don't see a reason to DROP the derby support in OFBiz and replace it
with docker. What we can and should do is to offer is a docker demo
besides this. There are already initiatives to do this.
In our experience, users already have problems with the simple build and
run OFBiz offers, it is not reasonable to make this more difficult for
them by having to install and run docker and OFBiz within.
Derby is not for production use, we state this clearly in the README's
and production setup guides. It is for demo purposes and easily
repeatable cleanAll/load scenarios which are also uses by buildbot for
the official demos..
If you not just want to have a brief look at the Demos, you'll have to
install Java anyway.
To use and load data into OFBiz, there is nothing more to do than
configuration in the entityengine.xml file as for any other database.
Derby is just the default.
Best regards,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 06.03.22 um 23:20 schrieb Development:
I added a new proposal on Jira . It is a proposal to drop support for derby
and use docker instead (You'll need to read the issue/proposal for that to make
sense) The issue is at: https://issues.apache.org/jira/browse/OFBIZ-12588
This is a copy of the proposal:
Derby is unique in the list of supported databases in that it lacks many
features that normal databases support, leading to Jira issues like:
https://issues.apache.org/jira/browse/OFBIZ-6138 . If you need specific
examples just ask.
Derby is already not recommended for production systems (which is good). I'm going to
speculate that the reason derby is supported is to have a easy way for people to download
ofbiz and "just run it" to get the demo running. Unfortunately this is not the
case now as java is often not installed anymore, and when it is installed, it's often the
wrong version of java for ofbiz.
I propose that we drop support for Derby and instead allow people to get the
demo easily running by making a official docker demo of the current stable
version that just comes with postgres in the docker image. (docker image is
being worked on here https://issues.apache.org/jira/browse/OFBIZ-10407 ).
Instead of requiring java to be installed, it would require docker to be
installed, but I believe the odds of success for a user are higher with docker
then dealing with the java version incompatibilities.
If you can think of a reason to keep derby after demos can be done through
docker, please add your comments.
CONFIDENTIALITY NOTICE: This message is intended only for the use of the person
or organization to which it is addressed or was intended to be addressed, and
may contain information that is privileged, confidential and exempt from
disclosure under applicable law. If the reader of this message is not the
intended recipient, or responsible for delivering the message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify the sender immediately by email and
delete the original message immediately . The sender, its subsidiaries and
affiliates, do not accept liability for any errors, omissions, corruption or
virus in the contents of this message or any attachments that arise as a result
of e-mail transmission. Thank you.
