[jira] [Commented] (OFBIZ-4153) Make entity engine a standalone database access tool/API

[Nicolas Malin (Jira)]

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

Mansour Al Akeel commented on OFBIZ-4153:
-----------------------------------------

I did sine research for similar functionlity. Having a standalone jar that can be used outside ofbiz adds a lot of value, because:
1- The entity engine can be used outside ofbiz and this will cause it to gain more popluarity.
2- It allows other containers to be used. For example, If I need to develop a component based on Spring, and integrate it with ofbiz, this will be possible.

I am not sure about the best approache to do this. But here's what seems to be the routes:
1- Refactor the EntityEngine and remove depedencies on other components.
2- Pick another framework that provides similar functionality, and develop an interface, to replace EntityEngine (ie Apache DDLUtils).

I didn't deeply thought about these routes. Other routes might exist and could be easier and provide a better solution.

Some references that can be useful:

https://cwiki.apache.org/confluence/display/OFBIZ/Running+a+standalone+entity+engine
http://ofbiz.135035.n4.nabble.com/Users-Isolating-and-Using-the-Entity-Engine-td142582.html
http://ofbiz.135035.n4.nabble.com/Getting-delegator-entity-engine-working-from-command-line-run-td151453.html




 

> Make entity engine a standalone database access tool/API
> --------------------------------------------------------
>
>                 Key: OFBIZ-4153
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4153
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Raj Saini
>            Assignee: Adam Heath
>            Priority: Minor
>
> From the user mailing list:
> I was picturing the entity engine as a lower level artifact - like a jar file. I don't have all of the details worked out yet, but what I picture is this:
> 1. An application needs a database-agnostic data store.
> 2. The application accesses the data store though the entity engine API/ jar library.
> Ofbiz has a very convenient way of defining databases, tables, and views as XML files. Plus, it has the ability to create/modify table/index structures during start-up. I believe that would be a very handy tool for anyone wanting to create any application that requires data storage.
> Wrapping the entity engine jar file in an OSGI bundle would be trivial.
> If anyone is interested in exploring this further, then they should create a Jira issue and we can take it from there.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)