Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between pages "Graphical Modeling Framework/Tutorial/Part 2" and "Equinox Slingshot"

< Graphical Modeling Framework‎ | Tutorial(Difference between pages)
m (→‎Feature Initializers)
 
 
Line 1: Line 1:
−
== Feature Initializers ==
+
The following are some random thoughts on the path forward for managing components in Eclipse/OSGi.
  
−
When you create a new element on a diagram, there is typically a domain element created or modified as a result.  In some cases, it's necessary to provide additional initialization information to ensure that objects are properly created.  For example, the links we create between topics in our mindmap diagram come in three flavors: dependency, includes, and extends. The 'type' attribute of the Relationship class is used to hold the RelationshipType enum value for the new instance.  In our graphical definition, we will create a figure and corresponding link for each type, along with a creation tool for each in our tooling definition.  We'll then use a feature sequence initilizer in our mapping definition to properly initialize our domain objects, depending on the type of link created on the diagram.
+
Existing technologies of interest:
 +
* Update Manager (of course :-)
 +
* OSGi Bundle Repository
 +
* Maven
 +
* DMS
 +
* UbiServ
  
−
Another possible initialization is to set the 'label' attribute of the Relationship as well, if the appearance of the link is not enough to distinguish between the types. 
 
  
−
[[Image:graph_links.png|right]]
 
  
−
First, create a three distinct polyline connections with properties and decorations as you see fit. For each add a connection for each of the new Dependency, Includes, and Extends links as shown in the figure. For each connection, create a Creation Tool in your mindmap.gmftool model.
 
  
−
<blockquote>
 
−
<font color="darkblue">'''Tip''' :</font> Don't forget that you can use copy/paste to duplicate elements in your models.  This will come in handy as you create three links, connections, tools, and mappings.
 
−
</blockquote>
 
  
−
<br style="clear:both;"/>
+
'''Mechanisms'''
 +
Component management needs some supporting mechanisms that are not currently present in Eclipse/OSGi.
 +
* overrides - the ability to have a "container" override values in the manifests etc. of the elements it contains.
  
−
[[Image:feature_init.png|right]]
+
* alien configuration managment
  
 +
* selectors - the ability to identify particular elements of a list as relevant only in particular scenarios or environments.  The Feature os= ws= etc attributes are an example.  If the current environment does not match those values then the associated feature element is ignored.  This mechanism should be generalized.
  
−
In the mapping model, for each of your Link Mappings, create a 'Feature Seq Initializer' element.  This will hold subsequent 'Feature Value Spec' elements as seen in the figure.  OCL is the language currently supported, so be careful that the body expressions you enter are valid.  In the case of initializing the enumeration field, you'll enter 'RelationshipType::DEPENDENCY' while in the case of initilizing the label attribute, you'll enter the string value within single quotes.  Keep in mind that the order of the 'Feature Value Spec' elements will determine the order in which they are executed.
 
  
−
<br style="clear:both;"/>
 
  
−
With these steps complete, we can regenerate our mindmap.gmfgen and code. When the diagram code is generated, below is what willl be generated within the Initializers inner class of MindmapElementTypes:
 
  
−
<pre>
+
Issues
−
public static final ObjectInitializer Relationship_3003 = new ObjectInitializer(
+
* Translations - Features need translation but they do not support fragments. Further, update is not able to download translations for features prior to the feature being downloaded. This makes sense as the  translation of features on sites
−
new FeatureInitializer[] {
+
−
new FeatureInitializer(
+
−
"RelationshipType::DEPENDENCY", //$NON-NLS-1$
+
−
MindmapPackage.eINSTANCE.getRelationship(),
+
−
MindmapPackage.eINSTANCE.getRelationship_Type()),
+
  
−
new FeatureInitializer(
+
- Source management
−
"'depends'", //$NON-NLS-1$
+
−
MindmapPackage.eINSTANCE.getRelationship(),
+
−
MindmapPackage.eINSTANCE
+
−
.getRelationship_Label())
+
  
−
});
+
- provisioning sites
−
</pre>
+
- has to be easy to
  
−
During link creation, the following code is executed in CreateIncomingRelationship3XXXCommand, found in the TopicItemSemanticEditPolicy class:
+
* Features - Features are different.  We end up with different infrastructure and different ways of expressing dependencies etc.  It may be useful to treat everything as a bundle.  That is not to say that features go away but rather their implementation merges with bundles. 
  
−
<pre>
 
−
protected EObject doDefaultElementCreation() {
 
−
Relationship newElement = (Relationship) super
 
−
.doDefaultElementCreation();
 
−
if (newElement != null) {
 
−
newElement.setTarget((Topic) getTarget());
 
−
newElement.setSource((Topic) getSource());
 
−
MindmapElementTypes.Initializers.Relationship_3004
 
−
.init(newElement);
 
−
}
 
−
return newElement;
 
−
}
 
−
</pre>
 
  
−
This generated code within FeatureInitializer will ultimately be called on each value spec you've added, which as you can see constructs an OCL query for evaluation and uses the result to initialize the field you selected.
+
Provisioning
  
−
<pre>
+
Agent
−
void init(EObject contextInstance) {
+
−
if (this.query == null) {
+
−
this.query = QueryFactory.eINSTANCE.createQuery(
+
−
expressionBody, contextClass);
+
−
}
+
−
Object value = query.evaluate(contextInstance);
+
−
if (sFeature.getEType() instanceof EEnum
+
−
&& value instanceof EEnumLiteral) {
+
−
value = ((EEnumLiteral) value).getInstance();
+
−
} else if (value != null && sFeature.isMany()) {
+
−
value = new BasicEList((Collection) value);
+
−
}
+
−
contextInstance.eSet(sFeature, value);
+
−
}
+
−
</pre>
+
  
−
<br style="clear:both;"/>
+
Feature/metamodel
  
−
[[Image:runtime_init.png|right]]
 
  
−
If you launch your runtime instance and test these new initializers, you will find that the type attribute is set according to the Relationship tool selected, and that the label attribute is preset to the names you defined above.
 
  
−
<br style="clear:both;"/>
+
Scenarios
 +
 
 +
- PDE
 +
 
 +
- Install
 +
 
 +
- Update
 +
 
 +
- Remote management
 +
 
 +
- Build

Latest revision as of 11:03, 4 February 2006

The following are some random thoughts on the path forward for managing components in Eclipse/OSGi.

Existing technologies of interest:

  • Update Manager (of course :-)
  • OSGi Bundle Repository
  • Maven
  • DMS
  • UbiServ



Mechanisms Component management needs some supporting mechanisms that are not currently present in Eclipse/OSGi.

  • overrides - the ability to have a "container" override values in the manifests etc. of the elements it contains.
  • alien configuration managment
  • selectors - the ability to identify particular elements of a list as relevant only in particular scenarios or environments. The Feature os= ws= etc attributes are an example. If the current environment does not match those values then the associated feature element is ignored. This mechanism should be generalized.



Issues

  • Translations - Features need translation but they do not support fragments. Further, update is not able to download translations for features prior to the feature being downloaded. This makes sense as the translation of features on sites

- Source management

- provisioning sites - has to be easy to

  • Features - Features are different. We end up with different infrastructure and different ways of expressing dependencies etc. It may be useful to treat everything as a bundle. That is not to say that features go away but rather their implementation merges with bundles.


Provisioning

Agent

Feature/metamodel


Scenarios

- PDE

- Install

- Update

- Remote management

- Build

Retrieved from "https://wiki.eclipse.org/index.php?title=Graphical_Modeling_Framework/Tutorial/Part_2&oldid=2093"

Back to the top