Hi Stephane, Etienne,
Happy New Year!
I would like to discuss with you the SCA introspection mechanism. I've
noticed that the implementation of java and composite introspection of
SCA components that you have provided is bound to the DnD
functionality for the SCA Composite Designer editor.
I would propose the following approach:
A definition of SCA Component Introspection interface that re-uses the
SCA Metamodel API for the result of the introspection process and uses
files for input.
If this pattern is followed then a new extension point shall be
defined (for the component introspection) and the DragAndDrop
extension point would be extended only once for introspection of SCA
Components. You could have another extensions for dragging and
dropping of other elements, e.g. Services - that would be WSDL file or
Java file, containing interface definition, are dropped onto a
component/composite reference or component/composite service in the
diagram.
Would you agree with refactoring of this part so that the
introspection itself is not bound or not dependent on graphical or
even editor related code?
Thanks in advance.
Best regards,
Bogdan
------------------------------------------------------------------------
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev