Eclipse Community Forums: MoDisco » MoDisco changing Model Load behavior

Help

Home

Home » Modeling » MoDisco » MoDisco changing Model Load behavior(Problem loading as Meta-Model Type)

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

MoDisco changing Model Load behavior [message #664871]

Tue, 12 April 2011 11:01

Anders Olsson

Messages: 21
Registered: July 2009

Junior Member

Hi,

What I'm trying to do is load a file according to my Meta-Model from code like so:

ResourceSet resourceSet = new ResourceSetImpl();
Resource myRes = resourceSet.createResource(myFileUri, MyMetaModelPackage.eNS_URI);
myRes.load(null);
EObject myObj = xmlRes.getContents().get(0);

myFileUri points to a file on the local filesystem. MyMetaModelPackage.eNS_URI contins the namespace of the Meta-Model.

In the case where the file extension is the expected (the one specified in the genmodel), things work as expected. myRes gets loaded as an XMIResource and myObj is of the expected Meta-Model type.

However if myFileUri points to a file with identical content, but with a different file extension, things behave differently. Then myRes gets the type 'org.eclipse.gmt.modisco.xml.resource.GenericXMLResourceImpl ' and myObj is a 'org.eclipse.gmt.modisco.xml.emf.impl.RootImpl' with the name of the first element in the model file.

Thing is if I uninstall MoDisco (version 0.8.2.v201102100957) and repeat the process where I load the file with the wrong file extension, things work just normal. I get an XMIResource, and the EObject I get out is of my Meta-Model type.

Is this a known bug in MoDisco, or is it expected behavior? Is there a way I should do my loading so MoDisco doesn't interfere?

Thanks in advance for any clarifications,

Anders

Report message to a moderator

Re: MoDisco changing Model Load behavior [message #664982 is a reply to message #664871]

Tue, 12 April 2011 16:22

Ed Merks

Messages: 33136
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------060500000507030903090101
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Anders,

Even if you make use of content types like the one registered for XMI

<extension
point="org.eclipse.core.contenttype.contentTypes">
<content-type
base-type="org.eclipse.core.runtime.xml"
* file-extensions="xmi"*
id="org.eclipse.emf.ecore.xmi"
name="%_UI_XMI_content_type"
priority="normal">
<describer
class=" org.eclipse.emf.ecore.xmi.impl.XMLContentHandlerImpl$XMI$Des criber "/>
</content-type>
</extension>

you still need to specify which file extensions to inspect for that type
of content. So it's up to you to ensure you have sufficient
registrations against extensions if that's sufficiently unique or a
combination of content types and extension (if you want to use xml as
your extension for example) to get the behavior you desire.

Anders Olsson wrote:
> Hi,
>
> What I'm trying to do is load a file according to my Meta-Model from
> code like so:
> ResourceSet resourceSet = new ResourceSetImpl();
> Resource myRes = resourceSet.createResource(myFileUri,
> MyMetaModelPackage.eNS_URI);
> myRes.load(null);
> EObject myObj = xmlRes.getContents().get(0);
>
> myFileUri points to a file on the local filesystem.
> MyMetaModelPackage.eNS_URI contins the namespace of the Meta-Model.
>
> In the case where the file extension is the expected (the one
> specified in the genmodel), things work as expected. myRes gets loaded
> as an XMIResource and myObj is of the expected Meta-Model type.
>
> However if myFileUri points to a file with identical content, but with
> a different file extension, things behave differently. Then myRes gets
> the type 'org.eclipse.gmt.modisco.xml.resource.GenericXMLResourceImpl
> ' and myObj is a 'org.eclipse.gmt.modisco.xml.emf.impl.RootImpl' with
> the name of the first element in the model file.
>
> Thing is if I uninstall MoDisco (version 0.8.2.v201102100957) and
> repeat the process where I load the file with the wrong file
> extension, things work just normal. I get an XMIResource, and the
> EObject I get out is of my Meta-Model type.
>
> Is this a known bug in MoDisco, or is it expected behavior? Is there a
> way I should do my loading so MoDisco doesn't interfere?
>
> Thanks in advance for any clarifications,
>
> Anders

--------------060500000507030903090101
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Anders, 
 
Even if you make use of content types like the one registered for XMI 
 
 <extension 
 point="org.eclipse.core.contenttype.contentTypes"> 
 <content-type 
 base-type="org.eclipse.core.runtime.xml" 
 file-extensions="xmi" 
 id="org.eclipse.emf.ecore.xmi" 
 name="%_UI_XMI_content_type" 
 priority="normal"> 
 <describer
class=" org.eclipse.emf.ecore.xmi.impl.XMLContentHandlerImpl$XMI$Des criber "/> 
 </content-type> 
</extension> 
 
you still need to specify which file extensions to inspect for that
type of content. So it's up to you to ensure you have sufficient
registrations against extensions if that's sufficiently unique or a
combination of content types and extension (if you want to use xml as
your extension for example) to get the behavior you desire. 
 
 
Anders Olsson wrote:
<blockquote cite="mid:io1avg$n8l$1@news.eclipse.org" type="cite">Hi,
 
 
What I'm trying to do is load a file according to my Meta-Model from
code like so:
 
ResourceSet resourceSet = new ResourceSetImpl();
 
Resource myRes = resourceSet.createResource(myFileUri,
MyMetaModelPackage.eNS_URI);
 
myRes.load(null);
 
EObject myObj = xmlRes.getContents().get(0);
 
 
myFileUri points to a file on the local filesystem.
MyMetaModelPackage.eNS_URI contins the namespace of the Meta-Model.
 
 
In the case where the file extension is the expected (the one specified
in the genmodel), things work as expected. myRes gets loaded as an
XMIResource and myObj is of the expected Meta-Model type.
 
 
However if myFileUri points to a file with identical content, but with
a different file extension, things behave differently. Then myRes gets
the type 'org.eclipse.gmt.modisco.xml.resource.GenericXMLResourceImpl
' and myObj is a 'org.eclipse.gmt.modisco.xml.emf.impl.RootImpl' with
the name of the first element in the model file.
 
 
Thing is if I uninstall MoDisco (version 0.8.2.v201102100957) and
repeat the process where I load the file with the wrong file extension,
things work just normal. I get an XMIResource, and the EObject I get
out is of my Meta-Model type.
 
 
Is this a known bug in MoDisco, or is it expected behavior? Is there a
way I should do my loading so MoDisco doesn't interfere?
 
 
Thanks in advance for any clarifications,
 
 
Anders
 
</blockquote>
</body>
</html>

--------------060500000507030903090101--

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

Report message to a moderator

Re: MoDisco changing Model Load behavior [message #665087 is a reply to message #664871]

Wed, 13 April 2011 08:38

Fabien Giquel

Messages: 147
Registered: July 2009

Senior Member

Hi Anders,

XMIResource factory is the default EMF registered factory for
deserializing a file, but the fact is that MoDisco registers one
specific factory for files with extensions "xml". I suppose the file you
try to load has an extension "xml" ... ?

Alongside Ed explanation and solution with additional global
registration based on contenttype/extension, i suggest to try this : you
may locally register in your ResourceSet one whished factory for your
file extension, which will override the global factories registrations.
So you may add the following 2th line in your program :

ResourceSet resourceSet = new ResourceSetImpl();

resourceSet.getExtensionToFactoryMap().put("MYFILEEXTENSION ", new
org.eclipse.emf.ecore.xmi.impl.XMIResourceFactoryImpl());

Resource myRes = resourceSet.createResource(myFileUri,
MyMetaModelPackage.eNS_URI);
myRes.load(null);
EObject myObj = xmlRes.getContents().get(0);

Fabien.

----------------------------------------------------
Fabien GIQUEL
R&D Engineer
Mia-Software
rue Nina Simone
44000 NANTES
----------------------------------------------------

Report message to a moderator

Re: MoDisco changing Model Load behavior [message #667201 is a reply to message #664871]

Wed, 27 April 2011 11:50

Anders Olsson

Messages: 21
Registered: July 2009

Junior Member

Hi,

thank you very much Fabien and Ed. Your replies were spot on: the file extension was XML when I tried to load the file. Clearly isn't a MoDisco problem, but rather me not registering the correct Factory. Thanks for the concrete example on how to do this as well.

Best Regards,

Anders

Report message to a moderator

Previous Topic:	MoDisco 0.8 Java Code Generation
Next Topic:	Welcome to eclipse.modisco

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 14:15:03 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter