Phil,

Comments below.

On 06/10/2011 5:55 PM, Phil Beauvoir wrote:
> I have a main Ecore model that is persisted to file in the following way:
>
>
> IArchimateModel model = ...;
> ResourceSet resourceSet = new ResourceSetImpl();
> Resource resource = resourceSet.createResource(uri);
> resource.getContents().add(model);
> resource.save(null);
>
>
> The method createResource(URI) in the Resource.Factory is over-ridden
> as follows:
>
>
> public Resource createResource(URI uri) {
> ArchimateResource result = new ArchimateResource(uri);
> result.getDefaultLoadOptions().putAll(getOptions());
> result.getDefaultSaveOptions().putAll(getOptions());
> return result;
> }
>
>
> In getOptions() I can set a number of tweaks to the xml format used in
> persistence:
>
>
> options = new HashMap<Object, Object>();
> ExtendedMetaData ext = new
> BasicExtendedMetaData(ExtendedMetaData.ANNOTATION_URI,
> EPackage.Registry.INSTANCE, new
> HashMap<EModelElement, EAnnotation>());
> ext.setName(IArchimatePackage.Literals.ARCHIMATE_MODEL, "model");
> // etc...
> options.put(XMLResource.OPTION_EXTENDED_META_DATA, ext);
>
>
> Now I have created a new Ecore model and package in a separate plug-in
> that extends the base Ecore model above with just a few additional
> classes. These classes are namespaced and when created by the user are
> added to a node of the base model. But this new model has its own
> Resource.Factory that never seems to be referenced when saving.
They're registered by extension so of course you'll have issues if you
have multiple registrations for the same extension (which are logged in
the Error Log). You can always use the debugger to find which factory
it's using.
> I would like to do a similar thing and provide default load and save
> options in ExtendedMetaData to this model's Resource.Factory.
>
> Am I missing something?
Missing a registrations or have duplicates...
>
> Thanks in advance.
>
> Phil

Phil,

It would seem better to have this meta data in the model at the time you
generate than to add it programmatically...

On 11/10/2011 9:28 AM, Phil Beauvoir wrote:
> Thanks Ed,
>
> yes the "parent" Resource is created but it doesn't know anything
> about the embedded "child" Ecore model. I figured out that it's best
> just to let the child model set its own Extended Metadata directly:
>
>
> // Ensure Package is initialised
> ICanvasPackage.eINSTANCE.eClass(); // The Iconic
> "imageData" attribute becomes an element
> ExtendedMetaData.INSTANCE.setFeatureKind(ICanvasPackage.Literals.ICONIC__IMAGE_DATA,
> ExtendedMetaData.ELEMENT_FEATURE);
>
> Phil

<sourceConnection xsi:type="archimate:Connection" id="8de80c5a" source="b2e81369" target="428b4832" relationship="2e12df54"/>

<sourceConnection xsi:type="archimate:Connection" id="8de80c5a" source="#b2e81369" target="#428b4832" relationship="#2e12df54"/>

Thanks again, Ed. I added EAnnotations to the elements in the ECore editor. Job done.

Once again this proves that EMF is the most well thought out framework. Ever.

Cheers,

Phil

public Resource createResource(URI uri) {
    Resource result = new ArchimateResource(uri);
    return result;
}

    public Resource createResource(URI uri) {
        XMLResource result = new ArchimateResource(uri);
        result.getDefaultSaveOptions().put(XMLResource.OPTION_EXTENDED_META_DATA, Boolean.TRUE);
        result.getDefaultLoadOptions().put(XMLResource.OPTION_EXTENDED_META_DATA, Boolean.TRUE);

        result.getDefaultSaveOptions().put(XMLResource.OPTION_SCHEMA_LOCATION, Boolean.TRUE);

        result.getDefaultLoadOptions().put(XMLResource.OPTION_USE_ENCODED_ATTRIBUTE_STYLE, Boolean.TRUE);
        result.getDefaultSaveOptions().put(XMLResource.OPTION_USE_ENCODED_ATTRIBUTE_STYLE, Boolean.TRUE);

        result.getDefaultLoadOptions().put(XMLResource.OPTION_USE_LEXICAL_HANDLER, Boolean.TRUE);
        return result;
    }

Phil,

Comments below.

On 15/10/2011 10:36 PM, Phil Beauvoir wrote:
> Unfortunately this has led to a curious side effect. When I was using
> the programmatic ExtendedMetadata, references to other objects' IDs in
> the persistence of a model instance looked like the following:
>
>
> <sourceConnection xsi:type="archimate:Connection" id="8de80c5a"

Is EAttribute.isID true for this?

> source="b2e81369" target="428b4832" relationship="2e12df54"/>
>
>
> But after the change, using the ExtendedMetadata annotations in the
> eCore model and generating the model, the persistence of a model
> instance now adds a hash (#) in front of each referenced ID:
>
>
> <sourceConnection xsi:type="archimate:Connection" id="8de80c5a"
> source="#b2e81369"

Is EReference.isResolveProxies true for this?

> target="#428b4832" relationship="#2e12df54"/>
>
>
> Why is the hash there now?

For something that could be a cross document reference in general but
the object is in the same resource so the resource URI needs to be
specified.

>
> Regards,
>
> Phil
>
>
> Phil Beauvoir wrote on Tue, 11 October 2011 15:13
>> Thanks again, Ed. I added EAnnotations to the elements in the ECore
>> editor. Job done.
>>
>> Once again this proves that EMF is the most well thought out
>> framework. Ever.
>>
>> Cheers,
>>
>> Phil
>
>