Eclipse Community Forums: Ecore Tools » [TEXO] move from normal EMF to TEXO

Help

Home

Home » Modeling » Ecore Tools » [TEXO] move from normal EMF to TEXO

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

[TEXO] move from normal EMF to TEXO [message #1038732]

Thu, 11 April 2013 08:38

Ludwig Moser

Messages: 450
Registered: July 2009

Senior Member

Hello!

i created a project with EMF ecore with hibernate. i ran into several problems so now want to move to Texo, which will resolve my problems.

fact is i have an .ecore and generated interfaces (which are used in several plugins of my application) and the Impl's to those interfaces.

after installing TEXO i generated model code, and looked at my src-gen folder,
which contains the Classes (they have no Impl attached) and contain class code.

what do i have to do to get Interfaces & Classes or how can i use my interfaces in these classes... so i can use them with my existing code? (i hope this is possible, otherwise i am in troubles.)

any help wellcome
thanks in advance
ludwig

Report message to a moderator

Re: [TEXO] move from normal EMF to TEXO [message #1041203 is a reply to message #1038732]

Sun, 14 April 2013 20:09

Martin Taal

Messages: 5468
Registered: July 2009

Senior Member

Hi Ludwig,
Strange I did not see your message in the newsgroup, the forum should get synced there...

Texo does not follow the interface pattern, so interfaces are only generated for eclasses defined as interfaces.

Actually afaics interfaces are not needed most of the time for entities. Why would you want to have/use interfaces?

gr. Martin

Report message to a moderator

Re: [TEXO] move from normal EMF to TEXO [message #1041430 is a reply to message #1041203]

Mon, 15 April 2013 05:05

Ludwig Moser

Messages: 450
Registered: July 2009

Senior Member

my application is split up into smaller parts (plugins)
and the specification for the objects used by these plugins are defined in interfaces
(the programmer does not need to know how data is retrieved. i have a StorageService, which provides different PersistenceServices. each of these PersistenceServices represent an concrete implementation. for exampe one saves its data in a XML file, another one can save it to a Database, how data-Structure is saved/mapped is up to the developer - important is the result!)

why do i do that? because all my data is currently stored in an database, which was designed like 15 years back, and its datastructure is not the way i want it to be. so i implemented a persistence service, which can load the data from this database. then i switch my persistence service to the new one and i can save it to my 'new' database with data structure without any problems.

Report message to a moderator

Previous Topic:	Ecore parser ?
Next Topic:	Diff 2 EObjects of the same ecore model

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Jul 20 00:57:18 GMT 2018

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter