Eclipse Community Forums: EMF » XMLResource only persists one root object

Help

Home

Home » Modeling » EMF » XMLResource only persists one root object(XMLResource only persists one root object)

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

XMLResource only persists one root object [message #997436]

Mon, 07 January 2013 13:59

Greg Babcock

Messages: 41
Registered: October 2012

Member

I have a simple application where I store multiple root objects in a resource. This worked with XMIResource, but when I switched to a XMLResource to take advantage of its uniqueID feature, only the first root object gets persisted.

I realize that this is probably the result of an XML rule limiting a document to a single root, are there any ways around it without resorting to multiple files?

Report message to a moderator

Re: XMLResource only persists one root object [message #997581 is a reply to message #997436]

Tue, 08 January 2013 13:07

Vlad Gheorghe

Messages: 127
Registered: May 2011

Senior Member

Hi Greg,

XMIResource extends XMLResource, so it inherits the useUUID feature.

In order to activate it you have to specialize XMIResourceImpl and override useIDs() to return true.

As for persisting to XML there are more strict requirements on the ecore (which include having a single root object per file).

Regards
Vlad

Report message to a moderator

Re: XMLResource only persists one root object [message #997653 is a reply to message #997436]

Mon, 07 January 2013 14:09

Christian Damus

Messages: 1270
Registered: July 2009
Location: Canada

Senior Member

Hi, Greg,

You can use XMIResource. It uses an <XMI> element at the root to
collect multiple objects; EMF elides it when loading.

HTH,

Christian

On 2013-01-07 13:59:34 +0000, Greg Babcock said:

> I have a simple application where I store multiple root objects in a
> resource. This worked with XMIResource, but when I switched to a
> XMLResource to take advantage of its uniqueID feature, only the first
> root object gets persisted.
> I realize that this is probably the result of an XML rule limiting a
> document to a single root, are there any ways around it without
> resorting to multiple files?

Report message to a moderator