You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Adam Heath (JIRA)" <ji...@apache.org> on 2014/06/25 18:44:25 UTC
[jira] [Assigned] (OFBIZ-4153) Make entity engine a standalone
database access tool/API
[ https://issues.apache.org/jira/browse/OFBIZ-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Heath reassigned OFBIZ-4153:
---------------------------------
Assignee: Adam Heath
> 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.2#6252)