Eclipse Community Forums: EMF Store

Help

Home

Home » Modeling » EMF Store » DB Persistence

Show: Today's Messages :: Show Polls :: Message Navigator

DB Persistence [message #699184]

Thu, 21 July 2011 03:13

Mike Haney

Messages: 25
Registered: June 2011

Junior Member

We have been evaluating EMFStore and it seems to fulfill most of our requirements for our new model-driven application platform. The only thing missing that I know will be a requirement for some projects is DB persistence. Many of our large enterprise customers would balk at storing their data as XML files somewhere on the server, so some type of ORM is definitely needed.

I noticed in the proposal document that it said the server could use EclipseLink for persistence, but I can't find any documentation on how to do this. Is this feature not implemented yet, or merely not documented yet?

Thanks,

Mike

Report message to a moderator

Re: DB Persistence [message #699277 is a reply to message #699184]

Thu, 21 July 2011 08:10

Eclipse User

Originally posted by: Jonas Helming

Hi Mike,
EMFStore has a abstract persistence layer, the default implementation is
XMI. 2 years ago, we had an implementation for DB based on Teneo. We
discovered, that due to the kind of read/write operations on the server
XMI was faster than the DB implementation. The server mostyl stores data
and quite seldom reads it again, mainly only if you access the history.
As a disadvantage, a DB back-end makes the model migration much more
complicated. If DB storage is required, that is definitly possible to
implement. Could you open a bug report in this case, to discuss this?
Cheers
Jonas

Am 21.07.2011 05:13, schrieb Mike Haney:
> We have been evaluating EMFStore and it seems to fulfill most of our
> requirements for our new model-driven application platform. The only
> thing missing that I know will be a requirement for some projects is DB
> persistence. Many of our large enterprise customers would balk at
> storing their data as XML files somewhere on the server, so some type of
> ORM is definitely needed.
>
> I noticed in the proposal document that it said the server could use
> EclipseLink for persistence, but I can't find any documentation on how
> to do this. Is this feature not implemented yet, or merely not
> documented yet?
>
> Thanks,
>
> Mike
>
>

Report message to a moderator

Re: DB Persistence [message #704557 is a reply to message #699277]

Thu, 28 July 2011 19:32

André B hlke

Messages: 14
Registered: July 2010

Junior Member

Hello,

could you use a Java Content Repository as persistence layer? What would have to be done? There is the JCRM project. Basically, you could implement the whole EmfStore interface using JCRM-APIs, right?

Would it be possible to delegate authentication and authorization to the JCR as well?

Thanks in advance!

Regards,

André

Report message to a moderator

Re: DB Persistence [message #713687 is a reply to message #704557]

Mon, 08 August 2011 19:38

Mike Haney

Messages: 25
Registered: June 2011

Junior Member

I looked at JCRM recently for another use, but it seems to be stalled (IP issues maybe?).

I think we've found a workaround for our issues using the default XMI persistence. All of our configuration data will be persisted in EMF store normally using XMI. To handle customer data that needs to be persisted in a database, we will create a separate persistence server component and pass the EMF model instances to it (probably will use Teneo inside the service to do the actual JPA mapping). Since our transactions are very workflow-oriented, this will work well for us and only requires adding a new step to the workflow.

Report message to a moderator

Previous Topic:	how to make AND operation between two conditions in EmfFacet
Next Topic:	Where can I find the sources?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Mar 02 15:17:30 GMT 2015

.:: Contact :: Home ::.