You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Michael Brohl (Jira)" <ji...@apache.org> on 2022/03/07 08:23:00 UTC

[jira] [Commented] (OFBIZ-12588) Drop Derby and support Docker instead (Yes, that's not a mistake)

    [ https://issues.apache.org/jira/browse/OFBIZ-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502127#comment-17502127 ] 

Michael Brohl commented on OFBIZ-12588:
---------------------------------------

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 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.

> Drop Derby and support Docker instead (Yes, that's not a mistake)
> -----------------------------------------------------------------
>
>                 Key: OFBIZ-12588
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12588
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: ddev
>            Priority: Major
>
> 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.
> (Note: is the "ofbiz/trunk" image on dockerhub a official version?)
> There is a patch related to the issue mentioned previously to add a docker build file at: https://github.com/apache/ofbiz-framework/pull/43/files/95a1230f2a80c822ca0d08e5825be44856821459
>  
> If you would like me to submit a patch to that patch to add postgres support and to make it load the demo data let me know and I will gladly write it.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)