|Re: [OCLinEcore] Error using EReference::EKeys property [message #558132 is a reply to message #558066]
||Fri, 10 September 2010 09:22
| Ed Willink
Registered: July 2009
The patch on https://bugs.eclipse.org/bugs/show_bug.cgi?id=324924 will
serialize a simple test file to
import ecore_0 : 'http://www.eclipse.org/emf/2002/Ecore#/';
package keys : ky = 'http://keys'
attribute r : ecore_0::EDouble[?];
attribute s : String[?];
property keyed : Keyed[*]
key r , s ;
which at least makes keys useable.
property keyed : Keyed[*|r,s];
On 10/09/2010 06:46, Ed Willink wrote:
> Hi Scott
> > Does this mean using EKeys is not supported?
> I'm afraid so. At least the error message is relevant. Actually they're
> half supported; the bidirectional conversion between Ecore and the
> OCLinCore Concrete Syntax is in place. It's the actual textual syntax
> that's missing.
> I plan to expand OCLinEcore to accommodate full class-like capabilities
> of UML and their idiomatic Ecore realisations. I just need to identify
> simple, consistent, memorable syntaxes.
> Since you are actually using keys you might have a suggestion or two. A
> patch might be quite easy.
> If you can send me an example Ecore file, that would help enlarge the
> gene pool of my test cases.
> Ed Willink
> On 10/09/2010 06:17, Scott wrote:
>> If I use the EReference::EKeys property in an ecore model, and then try
>> to open it with the OCLinEcore editor, I get:
>> Editor could not be initialized.
>> dConcreteSyntaxException: These errors need to be fixed before the model
>> can be serialized.
>> The feature OCLinEcoreReferenceCS.keys contains non-transient values but
>> has no corresponding assignment in rule ModelElementCS.
>> Does this mean using EKeys is not supported?
Powered by FUDForum
. Page generated in 0.09430 seconds