Eclipse Community Forums: EMF » OPTION_SCHEMA

Help

Home

Home » Modeling » EMF » OPTION_SCHEMA_LOCATION has no effect

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

OPTION_SCHEMA_LOCATION has no effect [message #1012268]

Thu, 21 February 2013 08:35

sakop qq

Messages: 29
Registered: January 2013

Junior Member

Hi,

In order to avoid the EPackage not found exception, I am saving xmi files using the option OPTION_SCHEMA_LOCATION:

Map options = new HashMap();
options.put(XMLResource.OPTION_SCHEMA_LOCATION,Boolean.TRUE);
file1.save(options);

Sometimes, it works fine since I can see the schemaLocation attribute in the generated file, however, there are still some occasions that this attribute is not generated, can sb tell me why?

Thanks

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1012294 is a reply to message #1012268]

Thu, 21 February 2013 09:32

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Maybe this answers the question: 
 
<li class="toclevel-2"><a
href="http://wiki.eclipse.org/index.php/EMF-FAQ#How_can_I_ensure_that_an_xsi:schemaLocation_is_serialized_for_my_packages.3F">2.22 How can I
ensure that an xsi:schemaLocation is serialized for my
packages?</a></li>
 
<div class="moz-cite-prefix">On 21/02/2013 9:35 AM, sakop qq wrote: 
</div>
<blockquote cite="mid:kg4m86$sh9$1@xxxxxxxxe.org" type="cite">Hi,
 
 
In order to avoid the EPackage not found exception, I am saving
xmi files using the option OPTION_SCHEMA_LOCATION:
 
 
Map options = new HashMap();
 

options.put(XMLResource.OPTION_SCHEMA_LOCATION,Boolean.TRUE);
 
file1.save(options);
 
 
 
Sometimes, it works fine since I can see the schemaLocation
attribute in the generated file, however, there are still some
occasions that this attribute is not generated, can sb tell me
why?
 
 
Thanks
 
</blockquote>
 
</body>
</html>

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

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1012716 is a reply to message #1012294]

Fri, 22 February 2013 05:03

sakop qq

Messages: 29
Registered: January 2013

Junior Member

It is really kind of you!

I have another question, would you please take a look at it?

I serialized a dynamic model,and below is a snippet of a EReference

<eStructuralFeatures xsi:type="ecore:EReference" name="items" upperBound="-1"
eType="ecore:EClass dynamic.ecore#//Item" containment="true" eOpposite="dynamic.ecore#//Item/order"/>

note that the eOpposite attribute has the segment "dynamic.ecore" before "#",however, the Eclass Item is declared within the same EPackage，namely in the same ecore file。

I expected the result to be as:
<eStructuralFeatures xsi:type="ecore:EReference" name="items" upperBound="-1"
eType="ecore:EClass dynamic.ecore#//Item" containment="true" eOpposite="#//Item/order"/>

How can I solve it？ Do I need to declare a certion option when saving it?

Thanks.

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1012809 is a reply to message #1012716]

Fri, 22 February 2013 09:03

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Comments below.

On 22/02/2013 6:03 AM, sakop qq wrote:
> It is really kind of you!
>
> I have another question, would you please take a look at it?
>
> I serialized a dynamic model,and below is a snippet of a EReference
>
> <eStructuralFeatures xsi:type="ecore:EReference" name="items"
> upperBound="-1"
> eType="ecore:EClass dynamic.ecore#//Item" containment="true"
> eOpposite="dynamic.ecore#//Item/order"/>
>
> note that the eOpposite attribute has the segment "dynamic.ecore"
> before "#",however, the Eclass Item is declared within the same
> EPackage，namely in the same ecore file。
Perhaps you loaded the resource with a non absolute? That's almost
always a bad idea.
>
> I expected the result to be as:
> <eStructuralFeatures xsi:type="ecore:EReference" name="items"
> upperBound="-1"
> eType="ecore:EClass dynamic.ecore#//Item" containment="true"
> eOpposite="#//Item/order"/>
>
> How can I solve it？ Do I need to declare a certion option when saving
> it?
If you load/create the resource with an absolute URI I don't think
you'll see what you're expecting/hoping to see.
>
> Thanks.

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

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1013391 is a reply to message #1012809]

Sat, 23 February 2013 14:56

sakop qq

Messages: 29
Registered: January 2013

Junior Member

So how can I persist the resource file in a relative way?

What I wanted to do is just eliminating the "segment" in the "eOpposite" attribute,how can I do that?

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1013417 is a reply to message #1013391]

Sat, 23 February 2013 16:04

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

What is the URI of the resource you serialized?

On 23/02/2013 3:56 PM, sakop qq wrote:
> So how can I persist the resource file in a relative way?
>
> What I wanted to do is just eliminating the "segment" in the
> "eOpposite" attribute,how can I do that?

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

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1013438 is a reply to message #1013417]

Sat, 23 February 2013 17:00

sakop qq

Messages: 29
Registered: January 2013

Junior Member

Resource r = rset.createResource(URI.createURI("dynamic.ecore"));

Thanks!

Report message to a moderator

Re: OPTION_SCHEMA_LOCATION has no effect [message #1013442 is a reply to message #1013438]

Sat, 23 February 2013 17:06

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Sakop,

That's what I thought and that why I told you to use an absolute URI.
If you're writing this to the workspace, you should use
URI.createPlatformResourceURI with the full path in the workspace; see
the FAQ. If you're running stand alone, you should use
URI.createFileURI with an absolute path in the file system, e.g., as
created by File.getAbsolutePath().

On 23/02/2013 6:00 PM, sakop qq wrote:
> Resource r = rset.createResource(URI.createURI("dynamic.ecore"));
>
> Thanks!

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

Report message to a moderator