Eclipse Community Forums: EMF » XML serialization of non-containment reference

Help

Home

Home » Modeling » EMF » XML serialization of non-containment reference

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

XML serialization of non-containment reference [message #418249]

Tue, 08 April 2008 17:57

Eclipse User

Originally posted by: joerg.von.frantzius.artnology.com

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi, 
 
in my model class "WithEObjectCopy", I have a non-containment reference
to some other class "NonContained" (in the same package). I'm creating
an XMLResource, and put a WithEObjectCopy object plus its referenced
NonContained object in it. When I serialize that to XML, I get the
following: 
<blockquote><tt><?xml version="1.0" encoding="UTF-8"?> 
<com.artnology.managedobject.test.eobjectcopy:WithEOb jectCopy
xmlns:com.artnology.managedobject.test.eobjectcopy=<a class="moz-txt-link-rfc2396E" href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>
someString="bla" nonContained="/1"> 
<contained someDate="2008-04-08T19:00:38.957+0200"/> 
</com.artnology.managedobject.test.eobjectcopy:WithEO bjectCopy> 
</tt></blockquote>
Obviously, the NonContained object is not written to the XML, although
it is being referenced. This is using dynamic EMF, i.e. I'm creating
EObjects using "ePackage.getEFactoryInstance().create(eClass)" with the
EPackage loaded from a .ecore file. 
 
My guess is that I need some kind of document root here, that I add the
two objects to. Unfortunately, I have no generated code to take that
from. Is there a "standard" way of having a (maybe artificial) document
root, with some arbitrary name? 
 
Maybe I can create a dynamic EClass that has a containment EReference
to WIthEObjectCopy plus a many-valued containment EReference to EObject
for anything referenced by non-containment, and use that as my document
root? 
 
I don't necessarily want to be able to deserialize the resulting XML. 
 
Thanks for any hints, 
Jörg 
</body>
</html>

Report message to a moderator

Re: XML serialization of non-containment reference [message #418250 is a reply to message #418249]

Tue, 08 April 2008 18:08

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------050005090207020403030108
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

J

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: XML serialization of non-containment reference [message #418251 is a reply to message #418250]

Tue, 08 April 2008 18:27

Eclipse User

Originally posted by: joerg.von.frantzius.artnology.com

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Ed, 
 
I already tried to figure out how that article could help me ;) 
 
For the records, in case anyone else has the same problem, here's what
my code does now: 
<blockquote><code> OutputStream out = ...; 
 EObject objectCopy = ...; 
 List<EObject> referenced = ...; // referenced by
non-containment 
 
 ResourceSet resourceSet = new ResourceSetImpl(); 
 final ExtendedMetaData extendedMetaData = new BasicExtendedMetaData(resourceSet.getPackageRegistry()); 
 resourceSet.getLoadOptions().put(XMLResource.OPTION_EXTENDED_META_DATA, extendedMetaData ); 
 EStructuralFeature rootNodeFeature = extendedMetaData.dem andFeature (getEPackage().getNsURI(), "rootNode", true); 
 ((EReference) rootNodeFeature).setUpperBound(EReference.UNBOUNDED_MULTIPLICITY); 
 EClass documentRootClass = rootNodeFeature.getEContaining Class (); 
 EObject documentRoot = EcoreUtil.create (documentRootClass); 
 List<EObject> contents = new ArrayList<EObject>(); 
 documentRoot.eSet(rootNodeFeature, contents); 
 
 // the URI in the following is a dummy, make up s omething that tells us something 
 // should we see it in the debugger 
 Resource writeXmlResource = XML_RESOURCE_FACTORY.createRe source (URI.createURI("tostream:" 
 + getManager().getModelInterface().getName() + "/" + getIdAsLong())); 
 
 contents.add(objectCopy); 
 // fix all DanglingHREfExceptions (objects that are r eferenced via non-containment associations) 
 for (EObject eObject :
referenced) { 
 if (eObject.eContainer() == null) { 
 //writeXmlResource.getContents().add(eObject); 
 contents.add(eObject); 
 } 
 } 
 
 documentRoot.eSet(rootNodeFeature, contents); 
 writeXmlResource.getContents().add(documentRoot); 
 writeXmlResource.save(out, saveOptions);</code></blockquote>
And this is a resulting XML: 
<blockquote><tt><?xml version="1.0" encoding="UTF-8"?> 
<eobjectcopy.ecore:DocumentRoot
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xmlns:eobjectcopy.ecore=<a class="moz-txt-link-rfc2396E" href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>> 
<rootNode xsi:type="eobjectcopy.ecore:WithEObjectCopy"
someString="bla" nonContained=<a class="moz-txt-link-rfc2396E" href="mailto://@rootNode.1">"//@rootNode.1"</a>> 
 <contained someDate="2008-04-08T20:17:49.168+0200"/> 
</rootNode> 
<rootNode xsi:type="eobjectcopy.ecore:NonContained"/> 
</eobjectcopy.ecore:DocumentRoot></tt> 
</blockquote>
That's a good start, thanks! 
 
Regards, 
Jörg 
 
Ed Merks schrieb:
<blockquote cite="mid:ftgcau$r8n$1@build.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
Jörg, 
 
Comments below. 
 
 
Jörg von Frantzius wrote:
<blockquote cite="mid:ftgbn3$f46$1@build.eclipse.org" type="cite">Hi, 
 
in my model class "WithEObjectCopy", I have a non-containment reference
to some other class "NonContained" (in the same package). I'm creating
an XMLResource, and put a WithEObjectCopy object plus its referenced
NonContained object in it. When I serialize that to XML, I get the
following: 
<blockquote><tt><?xml version="1.0" encoding="UTF-8"?> 
<com.artnology.managedobject.test.eobjectcopy:WithEOb jectCopy
xmlns:com.artnology.managedobject.test.eobjectcopy=<a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>
someString="bla" nonContained="/1"> 
<contained someDate="2008-04-08T19:00:38.957+0200"/> 
</com.artnology.managedobject.test.eobjectcopy:WithEO bjectCopy> 
</tt></blockquote>
Obviously, the NonContained object is not written to the XML, although
it is being referenced. This is using dynamic EMF, i.e. I'm creating
EObjects using "ePackage.getEFactoryInstance().create(eClass)" with the
EPackage loaded from a .ecore file. 
</blockquote>
An XMLResourceImpl won't save multiple roots. Only an XMIResourceImpl
can do that because it introduces a "fake" XMI root element. 
<blockquote cite="mid:ftgbn3$f46$1@build.eclipse.org" type="cite"> 
My guess is that I need some kind of document root here, that I add the
two objects to. Unfortunately, I have no generated code to take that
from. Is there a "standard" way of having a (maybe artificial) document
root, with some arbitrary name? 
</blockquote>
Yes, you need some type of container that can hold multiple children
and put your objects under it. Or use XMIResourceImpl. 
<blockquote cite="mid:ftgbn3$f46$1@build.eclipse.org" type="cite"> 
Maybe I can create a dynamic EClass that has a containment EReference
to WIthEObjectCopy plus a many-valued containment EReference to EObject
for anything referenced by non-containment, and use that as my document
root? 
</blockquote>
You can definitely demand create metadata for that type of thing. And
instance of AnyType could be used to contain multiple children. This
article will be helpful... 
<blockquote><a moz-do-not-send="true" target="_out"
href=" http://www.theserverside.com/tt/articles/article.tss?l=Bindi ngXMLJava">Binding
XML to Java</a></blockquote>
<blockquote cite="mid:ftgbn3$f46$1@build.eclipse.org" type="cite"> 
I don't necessarily want to be able to deserialize the resulting XML. 
 
Thanks for any hints, 
Jörg 
</blockquote>
 
</blockquote>
 
</body>
</html>

Report message to a moderator

Re: XML serialization of non-containment reference [message #418253 is a reply to message #418251]

Tue, 08 April 2008 20:00

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Jörg,

Comments below.

Jörg von Frantzius wrote:
> Hi Ed,
>
> I already tried to figure out how that article could help me ;)
>
> For the records, in case anyone else has the same problem, here's what
> my code does now:
>
> | OutputStream out = ...;
> EObject objectCopy = ...;
> List<EObject> referenced = ...; // referenced by non-containment
>
> ResourceSet resourceSet = *new *ResourceSetImpl();
> *final *ExtendedMetaData extendedMetaData = *new *BasicExtendedMetaData(resourceSet.getPackageRegistry());
> resourceSet.getLoadOptions().put(XMLResource.OPTION_EXTENDED _META_DATA, extendedMetaData);
> EStructuralFeature rootNodeFeature = extendedMetaData.demandFeature(getEPackage().getNsURI(), "rootNode", *true*);
> ((EReference) rootNodeFeature).setUpperBound(EReference.UNBOUNDED_MULTIPLI CITY);
> EClass documentRootClass = rootNodeFeature.getEContainingClass();
> EObject documentRoot = EcoreUtil.create(documentRootClass);
> List<EObject> contents = *new *ArrayList<EObject>();
> documentRoot.eSet(rootNodeFeature, contents);
> |
>
I'm surprised this works. I'd have figured you'd create a root feature,
put an AnyType instance under it, and then under that add two contained
children.
>
> |
> // the URI in the following is a dummy, make up something that tells us something
> // should we see it in the debugger
> Resource writeXmlResource = XML_RESOURCE_FACTORY.createResource(URI.createURI("tostream: "
> + getManager().getModelInterface().getName() + "/" + getIdAsLong()));
>
> contents.add(objectCopy);
> // fix all DanglingHREfExceptions (objects that are referenced via non-containment associations)
> *for *(EObject eObject : referenced) {
> *if *(eObject.eContainer() == *null*) {
> //writeXmlResource.getContents().add(eObject);
> contents.add(eObject);
> }
> }
>
> documentRoot.eSet(rootNodeFeature, contents);
> writeXmlResource.getContents().add(documentRoot);
> writeXmlResource.save(out, saveOptions);|
>
> And this is a resulting XML:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <eobjectcopy.ecore:DocumentRoot
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>
This tells me you're likely not using the extended meta data option to
save the result, and if you did you'd get invalid XML...
>
> xmlns:eobjectcopy.ecore="http:///com/artnology/managedobject/test/eobjectcopy.ecore">
> <rootNode xsi:type="eobjectcopy.ecore:WithEObjectCopy"
> someString="bla" nonContained="//@rootNode.1">
> <contained someDate="2008-04-08T20:17:49.168+0200"/>
> </rootNode>
> <rootNode xsi:type="eobjectcopy.ecore:NonContained"/>
> </eobjectcopy.ecore:DocumentRoot>
>
> That's a good start, thanks!
I feel like I'm bursting the balloon. I think it would be better to
create an any type root object, like above but eSet the anyType instance
to the root feature, and define a child element feature for which you'd
use anyType.getAny().add(<childFeature>, childObject)...
>
> Regards,
> Jörg
>
> Ed Merks schrieb:
>> Jörg,
>>
>> Comments below.
>>
>>
>> Jörg von Frantzius wrote:
>>> Hi,
>>>
>>> in my model class "WithEObjectCopy", I have a non-containment
>>> reference to some other class "NonContained" (in the same package).
>>> I'm creating an XMLResource, and put a WithEObjectCopy object plus
>>> its referenced NonContained object in it. When I serialize that to
>>> XML, I get the following:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> < com.artnology.managedobject.test.eobjectcopy:WithEObjectCopy
>>> xmlns:com.artnology.managedobject.test.eobjectcopy="http:///com/artnology/managedobject/test/eobjectcopy.ecore"
>>> someString="bla" nonContained="/1">
>>> <contained someDate="2008-04-08T19:00:38.957+0200"/>
>>> < /com.artnology.managedobject.test.eobjectcopy:WithEObjectCop y >
>>>
>>> Obviously, the NonContained object is not written to the XML,
>>> although it is being referenced. This is using dynamic EMF, i.e. I'm
>>> creating EObjects using
>>> "ePackage.getEFactoryInstance().create(eClass)" with the EPackage
>>> loaded from a .ecore file.
>> An XMLResourceImpl won't save multiple roots. Only an
>> XMIResourceImpl can do that because it introduces a "fake" XMI root
>> element.
>>>
>>> My guess is that I need some kind of document root here, that I add
>>> the two objects to. Unfortunately, I have no generated code to take
>>> that from. Is there a "standard" way of having a (maybe artificial)
>>> document root, with some arbitrary name?
>> Yes, you need some type of container that can hold multiple children
>> and put your objects under it. Or use XMIResourceImpl.
>>>
>>> Maybe I can create a dynamic EClass that has a containment
>>> EReference to WIthEObjectCopy plus a many-valued containment
>>> EReference to EObject for anything referenced by non-containment,
>>> and use that as my document root?
>> You can definitely demand create metadata for that type of thing.
>> And instance of AnyType could be used to contain multiple children.
>> This article will be helpful...
>>
>> Binding XML to Java
>> < http://www.theserverside.com/tt/articles/article.tss?l=Bindi ngXMLJava>
>>
>>>
>>> I don't necessarily want to be able to deserialize the resulting XML.
>>>
>>> Thanks for any hints,
>>> Jörg
>>
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: XML serialization of non-containment reference [message #418260 is a reply to message #418253]

Wed, 09 April 2008 09:01

Eclipse User

Originally posted by: joerg.von.frantzius.artnology.com

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello Ed, 
 
OK I tried using an AnyType and adding things to that. When I add them
to the AnyType individually, I get ugly references like
"<tt>//@rootNode/@mixed.2</tt>". I'm not sure yet whether it'll be easy
to use
that as XPath expressions in XSLT. What I would like to do here is
adding all referenced objects of the same class into the same
many-valued feature, with the feature named after the EClass'
uncapName. 
 
However, when I try to do the following: 
<blockquote><tt> for (EClass referencedClass :
referencedObjectsByClass.keySet()) { 
 EReference referencedContentFeature = (EReference)
extendedMetaData.demandFeature(getEPackage().getNsURI(), 

firstCharacterToLowerCase(referencedClass.getName()), true, true); 
 referencedContentFeature.setUpperBound(EReference.UNBOUNDED_ MULTIPLICITY) ; 
 final List<EObject> list =
referencedObjectsByClass.get(referencedClass); 
 anyType.getAny().add(referencedContentFeature, list); 
 } 
</tt></blockquote>
I get an exception 
<blockquote><tt>java.lang.ClassCastException: The feature
'nonContained's type 'EObject' does not permit a value of type
'java.util.ArrayList' 
 at
org.eclipse.emf.ecore.impl.EStructuralFeatureImpl$BasicFeatu reMapEntry.validate(EStructuralFeatureImpl.java:2891) 
 at
org.eclipse.emf.ecore.util.FeatureMapUtil.createEntry(Featur eMapUtil.java:180) 
 at
org.eclipse.emf.ecore.util.BasicFeatureMap.createEntry(Basic FeatureMap.java:101) 
 at
org.eclipse.emf.ecore.util.BasicFeatureMap.add(BasicFeatureM ap.java:1155) 
 at
org.eclipse.emf.ecore.util.FeatureMapUtil$FeatureFeatureMap. add(FeatureMapUtil.java:958) </tt> 
</blockquote>
Is it not possible to have a many-valued feature on a FeatureMap? In my
previous approach of adding everything directly on the DocumentRoot, I
was able to call 
<blockquote><tt>documentRoot.eSet(referencedContentFeature, list);</tt> 
</blockquote>
without problems. 
 
 
Ed Merks schrieb:
<blockquote cite="mid:ftgit3$k8j$1@build.eclipse.org" type="cite">Jörg,
 
 
Comments below.
 
 
Jörg von Frantzius wrote:
 
<blockquote type="cite">Hi Ed,
 
 
I already tried to figure out how that article could help me ;)
 
 
For the records, in case anyone else has the same problem, here's what
my code does now:
 
 
 | OutputStream out = ...;
 
 EObject objectCopy = ...;
 
 List<EObject> referenced = ...; // referenced by
non-containment
 
 
 ResourceSet resourceSet = *new *ResourceSetImpl();
 
 *final *ExtendedMetaData extendedMetaData = *new
*BasicExtendedMetaData(resourceSet.getPackageRegistry());
 

resourceSet.getLoadOptions().put(XMLResource.OPTION_EXTENDED _META_DATA,
extendedMetaData);
 
 EStructuralFeature rootNodeFeature =
extendedMetaData.demandFeature(getEPackage().getNsURI(), "rootNode",
*true*);
 
 ((EReference)
rootNodeFeature).setUpperBound(EReference.UNBOUNDED_MULTIPLI CITY);
 
 EClass documentRootClass =
rootNodeFeature.getEContainingClass();
 
 EObject documentRoot = EcoreUtil.create(documentRootClass);
 
 List<EObject> contents = *new
*ArrayList<EObject>();
 
 documentRoot.eSet(rootNodeFeature, contents);
 
 |
 
 
</blockquote>
I'm surprised this works. I'd have figured you'd create a root
feature, put an AnyType instance under it, and then under that add two
contained children.
 
<blockquote type="cite"> 
 |
 
 // the URI in the following is a dummy, make up something that
tells us something
 
 // should we see it in the debugger
 
 Resource writeXmlResource =
XML_RESOURCE_FACTORY.createResource(URI.createURI("tostream: "
 
 + getManager().getModelInterface().getName() + "/" +
getIdAsLong()));
 
 
 contents.add(objectCopy);
 
 // fix all DanglingHREfExceptions (objects that are referenced
via non-containment associations)
 
 *for *(EObject eObject : referenced) {
 
 *if *(eObject.eContainer() == *null*) {
 
 //writeXmlResource.getContents().add(eObject);
 
 contents.add(eObject);
 
 }
 
 }
 
 
 documentRoot.eSet(rootNodeFeature, contents);
 
 writeXmlResource.getContents().add(documentRoot);
 
 writeXmlResource.save(out, saveOptions);|
 
 
And this is a resulting XML:
 
 
 <?xml version="1.0" encoding="UTF-8"?>
 
 <eobjectcopy.ecore:DocumentRoot
 
 xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
 
 
</blockquote>
This tells me you're likely not using the extended meta data option to
save the result, and if you did you'd get invalid XML...
 
<blockquote type="cite"> 

xmlns:eobjectcopy.ecore=<a class="moz-txt-link-rfc2396E" href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>>
 
 <rootNode xsi:type="eobjectcopy.ecore:WithEObjectCopy"
 
 someString="bla" nonContained=<a class="moz-txt-link-rfc2396E" href="mailto://@rootNode.1">"//@rootNode.1"</a>>
 
 <contained someDate="2008-04-08T20:17:49.168+0200"/>
 
 </rootNode>
 
 <rootNode xsi:type="eobjectcopy.ecore:NonContained"/>
 
 </eobjectcopy.ecore:DocumentRoot>
 
 
That's a good start, thanks!
 
</blockquote>
I feel like I'm bursting the balloon. I think it would be better to
create an any type root object, like above but eSet the anyType
instance to the root feature, and define a child element feature for
which you'd use anyType.getAny().add(<childFeature>,
childObject)...
 
<blockquote type="cite"> 
Regards,
 
Jörg
 
 
Ed Merks schrieb:
 
<blockquote type="cite">Jörg,
 
 
Comments below.
 
 
 
Jörg von Frantzius wrote:
 
<blockquote type="cite">Hi,
 
 
in my model class "WithEObjectCopy", I have a non-containment reference
to some other class "NonContained" (in the same package). I'm creating
an XMLResource, and put a WithEObjectCopy object plus its referenced
NonContained object in it. When I serialize that to XML, I get the
following:
 
 
 <?xml version="1.0" encoding="UTF-8"?>
 
 <com.artnology.managedobject.test.eobjectcopy:WithEOb jectCopy
 

xmlns:com.artnology.managedobject.test.eobjectcopy=<a class="moz-txt-link-rfc2396E" href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>
 
 someString="bla" nonContained="/1">
 
 <contained someDate="2008-04-08T19:00:38.957+0200"/>
 

</com.artnology.managedobject.test.eobjectcopy:WithEO bjectCopy>
 
 
Obviously, the NonContained object is not written to the XML, although
it is being referenced. This is using dynamic EMF, i.e. I'm creating
EObjects using "ePackage.getEFactoryInstance().create(eClass)" with the
EPackage loaded from a .ecore file.
 
</blockquote>
An XMLResourceImpl won't save multiple roots. Only an XMIResourceImpl
can do that because it introduces a "fake" XMI root element.
 
<blockquote type="cite"> 
My guess is that I need some kind of document root here, that I add the
two objects to. Unfortunately, I have no generated code to take that
from. Is there a "standard" way of having a (maybe artificial) document
root, with some arbitrary name?
 
</blockquote>
Yes, you need some type of container that can hold multiple children
and put your objects under it. Or use XMIResourceImpl.
 
<blockquote type="cite"> 
Maybe I can create a dynamic EClass that has a containment EReference
to WIthEObjectCopy plus a many-valued containment EReference to EObject
for anything referenced by non-containment, and use that as my document
root?
 
</blockquote>
You can definitely demand create metadata for that type of thing. And
instance of AnyType could be used to contain multiple children. This
article will be helpful...
 
 
 Binding XML to Java
 

<a class="moz-txt-link-rfc2396E" href=" http://www.theserverside.com/tt/articles/article.tss?l=Bindi ngXMLJava">< http://www.theserverside.com/tt/articles/article.tss?l=Bindi ngXMLJava></a>
 
 
<blockquote type="cite"> 
I don't necessarily want to be able to deserialize the resulting XML.
 
 
Thanks for any hints,
 
Jörg
 
</blockquote>
 
</blockquote>
 
</blockquote>
</blockquote>
 
</body>
</html>

Report message to a moderator

Re: XML serialization of non-containment reference [message #418266 is a reply to message #418260]

Wed, 09 April 2008 11:22

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------050408090001020203080803
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

J

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: XML serialization of non-containment reference [message #418269 is a reply to message #418266]

Wed, 09 April 2008 11:41

Eclipse User

Originally posted by: joerg.von.frantzius.artnology.com

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ed Merks schrieb:
<blockquote cite="mid:fti8t5$q4n$1@build.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
Jörg, 
 
Comments below. 
 
Jörg von Frantzius wrote:
<blockquote cite="mid:fti0l6$i7a$1@build.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
<title></title>
Hello Ed, 
 
OK I tried using an AnyType and adding things to that. When I add them
to the AnyType individually, I get ugly references like
"<tt>//@rootNode/@mixed.2</tt>".</blockquote>
Hehehe. Beauty is in the eye of the beholder. If your objects has
EAttribute's for which isID is true, that value would be used instead... 
</blockquote>
Would that attribute have to be unique among everything within the same
resource, or does it suffice to have it unique among all objects of the
same class? The former, I'm afraid... 
<blockquote cite="mid:fti8t5$q4n$1@build.eclipse.org" type="cite">
<blockquote cite="mid:fti0l6$i7a$1@build.eclipse.org" type="cite">
I'm
not sure yet whether it'll be easy
to use
that as XPath expressions in XSLT. What I would like to do here is
adding all referenced objects of the same class into the same
many-valued feature, with the feature named after the EClass'
uncapName. 
</blockquote>
Yes, it would be quite cool to be able to support xpaths in general,
but such things often need to refer to namespaces and hence need to use
QNames where the prefix for the namespace is information known only to
the serializer... 
</blockquote>
Do you per chance know of a good approach to turn these references into
XPath expressions, like when trying to make use of the references in
XSLT? 
<blockquote cite="mid:fti8t5$q4n$1@build.eclipse.org" type="cite">
<blockquote cite="mid:fti0l6$i7a$1@build.eclipse.org" type="cite"> 
However, when I try to do the following: 
<blockquote><tt> for (EClass referencedClass :
referencedObjectsByClass.keySet()) { 
 EReference referencedContentFeature = (EReference)
extendedMetaData.demandFeature(getEPackage().getNsURI(), 

firstCharacterToLowerCase(referencedClass.getName()), true, true); 
 referencedContentFeature.setUpperBound(EReference.UNBOUNDED_ MULTIPLICITY) ; 
 final List<EObject> list =
referencedObjectsByClass.get(referencedClass); 
 anyType.getAny().add(referencedContentFeature, list); 
</tt></blockquote>
</blockquote>
<tt>//
referencedContentFeature.setUpperBound(EReference.UNBOUNDED_ MULTIPLICITY) ; 
// final List<EObject> list =
referencedObjectsByClass.get(referencedClass); 
// anyType.getAny().add(referencedContentFeature, list); 
 
</tt><tt>for (EObject eObject : </tt><tt>referencedObjectsByClass.get(referencedClass)) 
{ 
</tt><tt> anyType.getAny().add(referencedContentFeature, eObject); 
} 
</tt>
<blockquote cite="mid:fti0l6$i7a$1@build.eclipse.org" type="cite">
<blockquote><tt> } 
</tt></blockquote>
I get an exception 
<blockquote><tt>java.lang.ClassCastException: The feature
'nonContained's type 'EObject' does not permit a value of type
'java.util.ArrayList' 
 at
org.eclipse.emf.ecore.impl.EStructuralFeatureImpl$BasicFeatu reMapEntry.validate(EStructuralFeatureImpl.java:2891) 
 at
org.eclipse.emf.ecore.util.FeatureMapUtil.createEntry(Featur eMapUtil.java:180) 
 at
org.eclipse.emf.ecore.util.BasicFeatureMap.createEntry(Basic FeatureMap.java:101) 
 at
org.eclipse.emf.ecore.util.BasicFeatureMap.add(BasicFeatureM ap.java:1155) 
 at
org.eclipse.emf.ecore.util.FeatureMapUtil$FeatureFeatureMap. add(FeatureMapUtil.java:958) </tt> 
</blockquote>
Is it not possible to have a many-valued feature on a FeatureMap? In my
previous approach of adding everything directly on the DocumentRoot, I
was able to call 
<blockquote><tt>documentRoot.eSet(referencedContentFeature, list);</tt> 
</blockquote>
without problems. 
</blockquote>
No. Even for a multi-valued feature, the feature map entry is still a
feature single value pair. I.e., the value of the feature map entry
must always be a value of the features type and the
multiplicity affects only whether it's valid to have multiple such
entries in the feature map. 
<blockquote cite="mid:fti0l6$i7a$1@build.eclipse.org" type="cite"> 
 
Ed Merks schrieb:
<blockquote cite="mid:ftgit3$k8j$1@build.eclipse.org" type="cite">Jörg,
 
 
Comments below. 
 
Jörg von Frantzius wrote: 
<blockquote type="cite">Hi Ed, 
 
I already tried to figure out how that article could help me ;) 
 
For the records, in case anyone else has the same problem, here's what
my code does now: 
 
 | OutputStream out = ...; 
 EObject objectCopy = ...; 
 List<EObject> referenced = ...; // referenced by
non-containment 
 
 ResourceSet resourceSet = *new *ResourceSetImpl(); 
 *final *ExtendedMetaData extendedMetaData = *new
*BasicExtendedMetaData(resourceSet.getPackageRegistry()); 

resourceSet.getLoadOptions().put(XMLResource.OPTION_EXTENDED _META_DATA,
extendedMetaData); 
 EStructuralFeature rootNodeFeature =
extendedMetaData.demandFeature(getEPackage().getNsURI(), "rootNode",
*true*); 
 ((EReference)
rootNodeFeature).setUpperBound(EReference.UNBOUNDED_MULTIPLI CITY); 
 EClass documentRootClass =
rootNodeFeature.getEContainingClass(); 
 EObject documentRoot = EcoreUtil.create(documentRootClass); 
 List<EObject> contents = *new
*ArrayList<EObject>(); 
 documentRoot.eSet(rootNodeFeature, contents); 
 | 
 
</blockquote>
I'm surprised this works. I'd have figured you'd create a root
feature, put an AnyType instance under it, and then under that add two
contained children. 
<blockquote type="cite"> 
 | 
 // the URI in the following is a dummy, make up something that
tells us something 
 // should we see it in the debugger 
 Resource writeXmlResource =
XML_RESOURCE_FACTORY.createResource(URI.createURI("tostream: " 
 + getManager().getModelInterface().getName() + "/" +
getIdAsLong())); 
 
 contents.add(objectCopy); 
 // fix all DanglingHREfExceptions (objects that are referenced
via non-containment associations) 
 *for *(EObject eObject : referenced) { 
 *if *(eObject.eContainer() == *null*) { 
 //writeXmlResource.getContents().add(eObject); 
 contents.add(eObject); 
 } 
 } 
 
 documentRoot.eSet(rootNodeFeature, contents); 
 writeXmlResource.getContents().add(documentRoot); 
 writeXmlResource.save(out, saveOptions);| 
 
And this is a resulting XML: 
 
 <?xml version="1.0" encoding="UTF-8"?> 
 <eobjectcopy.ecore:DocumentRoot 
 xmlns:xsi=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
 
 
</blockquote>
This tells me you're likely not using the extended meta data option to
save the result, and if you did you'd get invalid XML... 
<blockquote type="cite"> 

xmlns:eobjectcopy.ecore=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>>
 
 <rootNode xsi:type="eobjectcopy.ecore:WithEObjectCopy" 
 someString="bla" nonContained=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto://@rootNode.1">"//@rootNode.1"</a>>
 
 <contained someDate="2008-04-08T20:17:49.168+0200"/> 
 </rootNode> 
 <rootNode xsi:type="eobjectcopy.ecore:NonContained"/> 
 </eobjectcopy.ecore:DocumentRoot> 
 
That's a good start, thanks! 
</blockquote>
I feel like I'm bursting the balloon. I think it would be better to
create an any type root object, like above but eSet the anyType
instance to the root feature, and define a child element feature for
which you'd use anyType.getAny().add(<childFeature>,
childObject)... 
<blockquote type="cite"> 
Regards, 
Jörg 
 
Ed Merks schrieb: 
<blockquote type="cite">Jörg, 
 
Comments below. 
 
 
Jörg von Frantzius wrote: 
<blockquote type="cite">Hi, 
 
in my model class "WithEObjectCopy", I have a non-containment reference
to some other class "NonContained" (in the same package). I'm creating
an XMLResource, and put a WithEObjectCopy object plus its referenced
NonContained object in it. When I serialize that to XML, I get the
following: 
 
 <?xml version="1.0" encoding="UTF-8"?> 
 <com.artnology.managedobject.test.eobjectcopy:WithEOb jectCopy 

xmlns:com.artnology.managedobject.test.eobjectcopy=<a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="http:///com/artnology/managedobject/test/eobjectcopy.ecore">"http:///com/artnology/managedobject/test/eobjectcopy.ecore"</a>
 
 someString="bla" nonContained="/1"> 
 <contained someDate="2008-04-08T19:00:38.957+0200"/> 

</com.artnology.managedobject.test.eobjectcopy:WithEO bjectCopy> 
 
Obviously, the NonContained object is not written to the XML, although
it is being referenced. This is using dynamic EMF, i.e. I'm creating
EObjects using "ePackage.getEFactoryInstance().create(eClass)" with the
EPackage loaded from a .ecore file. 
</blockquote>
An XMLResourceImpl won't save multiple roots. Only an XMIResourceImpl
can do that because it introduces a "fake" XMI root element. 
<blockquote type="cite"> 
My guess is that I need some kind of document root here, that I add the
two objects to. Unfortunately, I have no generated code to take that
from. Is there a "standard" way of having a (maybe artificial) document
root, with some arbitrary name? 
</blockquote>
Yes, you need some type of container that can hold multiple children
and put your objects under it. Or use XMIResourceImpl. 
<blockquote type="cite"> 
Maybe I can create a dynamic EClass that has a containment EReference
to WIthEObjectCopy plus a many-valued containment EReference to EObject
for anything referenced by non-containment, and use that as my document
root? 
</blockquote>
You can definitely demand create metadata for that type of thing. And
instance of AnyType could be used to contain multiple children. This
article will be helpful... 
 
 Binding XML to Java 
 <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href=" http://www.theserverside.com/tt/articles/article.tss?l=Bindi ngXMLJava">< http://www.theserverside.com/tt/articles/article.tss?l=Bindi ngXMLJava></a>
 
 
<blockquote type="cite"> 
I don't necessarily want to be able to deserialize the resulting XML. 
 
Thanks for any hints, 
Jörg 
</blockquote>
 
</blockquote>
 
</blockquote>
</blockquote>
 
</blockquote>
 
</blockquote>
 
</body>
</html>

Report message to a moderator

Re: XML serialization of non-containment reference [message #418271 is a reply to message #418269]

Wed, 09 April 2008 11:56

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------070808090602070500000000
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

J

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	How to get modified model objects
Next Topic:	How to get path of workbench

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 04:02:22 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter