Hi Johnson,
I would need one short technical discussion with the
community on the topic first.
What I
currently have is a particular set (the complete one for now) of the SCA XSDs
imported as one monolithic EMF model. It is completely ok for me right now but I
see problems in the future when somebody decides to define new SCA
implementation or binding type. Then if we go with the current approach each
extension of the SCA spec/standard will force us to recreate the metamodel (EMF
model). I would recommend to discontinue the monolitic approach and define
separate metamodels (with some references between them) based on a single XSD
from the SCA spec. This would lead to a set of EMF models (15 for now). It is
not a challenge to define 15 EMF models (the XSDs are defined) but I would like
to ask whether the community would be comfortable with such an
approach.
I would like to
discuss that point, make the proper changes
if decided, and then to attaching the code to bugzilla
entry.
Best regards,
Bogdan
Hi Bogdan,
Thanks for your help to updating the core model to
SCA1.0.
According to the dev plan from stp pmcc, we are
going to integrate other existing components and new contributions
based on the sca core model after Eclipse Europa
release (June 2007).
Would you please create a patch and attach it
to the bug?
Since Adrian is on vacation now. I am glad to apply
the patch on behalf of you.
Best Regards
Johnson
----- Original Message -----
Sent: Monday, May 28, 2007 3:38 PM
Subject: [stp-dev] SCA v1.0
Hi
Adrian,
Do you have any
progress on that? Is it possible for me to help you with this
issue?
Actually I have
the SCA v1.0 metamodel already imported (from XSD) as EMF model and I am using
it locally for our SCA design-time implementation.
Do you think it is
meaningful to send you what I have for the sca1.0 emf based
meta-model?
This particular
problem is the key point for us to start extending the STP framework.
Currently we do not extend (or even re-use on API basis) any STP
part but we would like to do so.
(Un)fortunatelly
we needed SCA v1.0 for our SCA design-time support for the SCA runtime that we
are implementing and I had to create the sca 1.0
metamodel.
Now I would like
to have it inside STP and actually start using the entire platform, extend
extension points, propose new extension points etc.
Best
regards,
Bogdan
_______________________________________________ stp-dev mailing
list stp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/stp-dev
|