|
| Re: [CDO] Modify an existing emf Project(UML2) to CDO [message #426298 is a reply to message #426297] |
Mon, 22 December 2008 15:28   |
 Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Hi Jörg,
unfortunately, legacy models are not yet supported in CDO 2.0.0:
247226: Transparently support legacy models
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247226
it depends on a new feature in EMF 2.5.0, Ed and Eike are working on it:
247130: Provide vetoable notification for read and write access
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247130
(btw, you can take a look at the different categories of models
supported by CDO at http://wiki.eclipse.org/CDO_Client).
However, I feel your case is a bit more complicated. I believe MDT UML2
model extends Ecore (I tried once!). This would imply registering in
CDOSession the Ecore model, which can not be generated for CDO (circular
dependency on plugin level). We would need the "Provide vetoable
notification for read and write access" bug for Ecore, but it incurs to
some performance issues.
Maybe Ed or Eike could shed some light over this issue.
Regards,
Victor.
Jörg escribió:
> Hello,
>
> it is possible to change an existing emf project to cdo without
> regenerating the code? I need this for uml2 editors from the cvs
> org.eclipse.mdt->org.eclipse.uml2->plugins->org.eclipse.uml2.uml . How
> complexity is it and where i have to change the code?
>
> Greetings
|
|
|
| Re: [CDO] Modify an existing emf Project(UML2) to CDO [message #426300 is a reply to message #426298] |
Mon, 22 December 2008 17:19 |
|
Guys,
Basically everything Vik said is right. During ESE I talked to Kenn
Hussey and he pointed out several times that he's very interested in CDO
support for UML2. I have no clue about concrete plans and I suggest to
ask on the UML2 newsgroup, too, to signal interest in this integration.
Btw. the wiki page Vik mentioned is not up to date regarding legacy
model support. Currently there is absolutely no support for generated
non-CDO models (i.e. legacy models) and when we develop it, it won't
have the characteristics mentioned in the table. The table stems from a
former AspectJ-based approach to legacy model support which had been
terminated.
Cheers
/Eike
----
http://thegordian.blogspot.com
Víctor Roldán Betancort schrieb:
> Hi Jörg,
>
> unfortunately, legacy models are not yet supported in CDO 2.0.0:
>
> 247226: Transparently support legacy models
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=247226
>
> it depends on a new feature in EMF 2.5.0, Ed and Eike are working on it:
>
> 247130: Provide vetoable notification for read and write access
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=247130
>
> (btw, you can take a look at the different categories of models
> supported by CDO at http://wiki.eclipse.org/CDO_Client).
>
> However, I feel your case is a bit more complicated. I believe MDT
> UML2 model extends Ecore (I tried once!). This would imply registering
> in CDOSession the Ecore model, which can not be generated for CDO
> (circular dependency on plugin level). We would need the "Provide
> vetoable notification for read and write access" bug for Ecore, but it
> incurs to some performance issues.
>
> Maybe Ed or Eike could shed some light over this issue.
>
> Regards,
> Victor.
>
> Jörg escribió:
>> Hello,
>>
>> it is possible to change an existing emf project to cdo without
>> regenerating the code? I need this for uml2 editors from the cvs
>> org.eclipse.mdt->org.eclipse.uml2->plugins->org.eclipse.uml2.uml .
>> How complexity is it and where i have to change the code?
>>
>> Greetings
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.03087 seconds
] 
Search
Help
Register
Login
Home
