| RE: [stp-dev] SCA v1.0 |
|
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 From: stp-dev-bounces@xxxxxxxxxxx [mailto:stp-dev-bounces@xxxxxxxxxxx] On Behalf Of Johnson Ma Sent: Tuesday, May 29, 2007 3:49 AM To: STP Dev list Subject: Re: [stp-dev] SCA v1.0 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
|