|Re: Additional behaviors for SCA designer [message #577002 is a reply to message #576979]
||Tue, 18 May 2010 11:31
| Stephane Drapeau
Registered: July 2009
Yes, you can extend the SCA meta model to include additional elements on
components, services and references. You can also add a property tab
displaying those elements (not a widget on the graphical representation).
There is a sample on the svn . This sample provides an extension 
to add SAWSDL annotations on SCA elements. Have a look to the following
plugins: org.eclipse.stp.sca.semantic.sawsdl and
To implement your own extension:
- First, create an ecore model describing your extension and generate
the code. Your elements must extend the EClass named AnyExtension
(defined in the SCA meta model). You must also add an element that
extends DocumentRoot. Have a look to the SAWSDL meta model defined in
- Then, create a class that extends IFilter and a class that extends
ScaPropertySectionProvider. Define also the extensions needed. Have a
look to org.eclipse.stp.sca.semantic.sawsdl.edit/customsrc and to plugin.xml
Currently, this extension mechanism is only available with the OSOA meta
model (not with the OASIS one).
Ian.Edward.Thomas@rmit.edu.au a écrit :
> Is it possible to extend the SCA Composite Designer Plugin beyond the
> defined extension points for interface, implementation and bindings,
> defined in org.eclipse.stp.sca.diagram.extension.* ?
> Specifically, is there a (safe) way to extend the diagrams to include
> additional widgets beyond the services and references etc. I can
> extend the SCA meta model to include additional elements and include
> those tags in the *.composite XML, but am unsure whether there is way
> into the designer plugin to allow new types of widgets to be added to
> and be manipulated in the existing SCA composite diagrams.
> There is research in annotating architecture diagrams with additional
> behaviour or modelling information, such as time and space estimates.
> Being able to annotate this additional information would allow the
> representation of non-functional behaviour for SCA architectures and
> allow analysis tools to analyse this information at runtime.
> Assuming this is not possible currently, would this be useful extension
> to the designer framework?
> Any suggestions?
Powered by FUDForum
. Page generated in 0.02283 seconds