[
https://issues.apache.org/jira/browse/OFBIZ-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988137#action_12988137
]
Adrian Crum commented on OFBIZ-4153:
------------------------------------
Some preliminary work was done on this idea in a branch:
https://svn.apache.org/repos/asf/ofbiz/branches/executioncontext20090716
That branch is a little old, and the changes in it encompass more than just the
entity engine, but it should provide some general direction for this effort.
> 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
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
