| Handling of very large model instances using Teneo [message #608625] |
Tue, 03 July 2007 06:49 |
 Robert Enyedi
Messages: 68
Registered: July 2009 |
Member |
|
|
Hi,
This is a question that I already asked in the EMF newsgroup, but I
would like to know what the advantages of Teneo are for this scenario
compared to XMI serialization.
I'm investigating EMF's ability to deal with very large model instances
which as a whole might not fit in the memory.
My usage scenario is similar to this one: Container (1) -> (*) Component
(one container holding many components). I have only one container. A
small number of components do fit in the memory, however the container
with all its components might not. A crucial thing is that the
components can have cross references among themselves.
It has been confirmed that for XMI serialization I can make use of the
org.eclipse.emf.ecore.resource.Resource class and save the components in
separate XMI files. The container can also be saved to a separate XMI
file by using non-containment references to its components.
Can I do the same model instance split with Teneo? Further more, is EMFT
Teneo of any help in managing the in-memory objects or should I make use
of a caching library instead?
Regards,
Robert
|
|
|
Powered by
FUDForum. Page generated in 0.02579 seconds
] 
Search
Help
Register
Login
Home
