Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » OCL » [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSet
[OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSet [message #1075407] Mon, 29 July 2013 07:22 Go to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
Hi,

I have problems using a "Setting Delegate" for providing the initial value of an EAttribute (type: EInt).

I use the following Model (class and its attributes)

MyClass
-> myAttribute : EInt
-> myAttributeWithInitialValue : EInt
OCL Setting Delegate:
Source = "http://www.eclipse.org/emf/2002/Ecore/OCL"
Key = "initial"
Value = 100

Actually, the setting delegate works, i.e. when creating an object of type MyClass it has an attribute "myAttributeWithInitialValue" with value "100". However, it is not possible to set the value of "myAttributeWithInitialValue" any more (=> UnsupportedOperationException). Changing the value of "myAttribute" is possible, of course.

I debugged into it and found the problem: for "myAttributeWithInitialValue" and "myAttribute" the method "dynamicSet" is called, which again uses the delegate for setting the value. However, for "myAttributeWithInitialValue" the delegate is an object of type "OCLSettingDelegate" which does not provide the setting of values. In my opinion, this is meaningful for delegate type "derive", but not for "initial" (both OCL setting delegates).

I don't understand the behavior... Is this a bug or a feature?
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSet [message #1075597 is a reply to message #1075407] Mon, 29 July 2013 14:08 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4003
Registered: July 2009
Senior Member
Hi

You don't provide me enough information to make any useful comment.

Your model is in no language that I recognize and not one that I can load.

OCLSettingDelegate has no package path so I can't tell what that is either.

Zipping up an example project will generally me and ytou a lot of time.

Regards

Ed Willink

On 29/07/2013 12:22, Kirsten M. Z. wrote:
> Hi,
>
> I have problems using a "Setting Delegate" for providing the initial
> value of an EAttribute (type: EInt).
>
> I use the following Model (class and its attributes)
>
> MyClass
> -> myAttribute : EInt
> -> myAttributeWithInitialValue : EInt
> OCL Setting Delegate:
> Source = "http://www.eclipse.org/emf/2002/Ecore/OCL"
> Key = "initial"
> Value = 100
>
> Actually, the setting delegate works, i.e. when creating an object of
> type MyClass it has an attribute "myAttributeWithInitialValue" with
> value "100". However, it is not possible to set the value of
> "myAttributeWithInitialValue" any more (=>
> UnsupportedOperationException). Changing the value of "myAttribute" is
> possible, of course.
>
> I debugged into it and found the problem: for
> "myAttributeWithInitialValue" and "myAttribute" the method
> "dynamicSet" is called, which again uses the delegate for setting the
> value. However, for "myAttributeWithInitialValue" the delegate is an
> object of type "OCLSettingDelegate" which does not provide the setting
> of values. In my opinion, this is meaningful for delegate type
> "derive", but not for "initial" (both OCL setting delegates).
>
> I don't understand the behavior... Is this a bug or a feature?
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSet [message #1075674 is a reply to message #1075597] Mon, 29 July 2013 17:01 Go to previous messageGo to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
> Hi
>
> You don't provide me enough information to make any useful comment.
>
> Your model is in no language that I recognize and not one that I can load.
>
> OCLSettingDelegate has no package path so I can't tell what that is either.
>
> Zipping up an example project will generally me and ytou a lot of time.
>
> Regards
>
> Ed Willink


Attached an example project which uses exactly the stuff I posted... have no idea why I get the exception (actually I can debug and see it, but still no idea if there SHOULD be the exception).

  • Attachment: test.rar
    (Size: 10.27KB, Downloaded 26 times)
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSe [message #1075810 is a reply to message #1075674] Tue, 30 July 2013 01:36 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4003
Registered: July 2009
Senior Member
Hi

This appears to be an EMF bug fixed in Kepler; you didn't say what you
are using.

If I regenerate your model, it no longer attempts to use setting
delegates for non-derived property actions.

The results are then

0
0
0
200

[OCL Settting Delegates do not support set, since OCL does not support
model mutation within OCL expressions.]

Regards

Ed Willink


On 29/07/2013 22:01, Kirsten M. Z. wrote:
>> Hi
>>
>> You don't provide me enough information to make any useful comment.
>>
>> Your model is in no language that I recognize and not one that I can load.
>>
>> OCLSettingDelegate has no package path so I can't tell what that is either.
>>
>> Zipping up an example project will generally me and ytou a lot of time.
>>
>> Regards
>>
>> Ed Willink
>
> Attached an example project which uses exactly the stuff I posted... have no idea why I get the exception (actually I can debug and see it, but still no idea if there SHOULD be the exception).
>
>
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSe [message #1075820 is a reply to message #1075810] Tue, 30 July 2013 02:12 Go to previous messageGo to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
Ahhh... unfortunately not all version information is in the project.

However, I use Kepler. I will copy some version Information. Can you see any important difference to your version?

Version: Kepler Release
Build id: 20130614-0229

EMF - Eclipse Modeling Framework SDK 2.9.0.v20130610-0406 org.eclipse.emf.sdk.feature.group Eclipse Modeling Project
EMF - Eclipse Modeling Framework Xcore SDK 1.1.0.v20130612-0809 org.eclipse.emf.ecore.xcore.sdk.feature.group Eclipse Modeling Project
EMF Compare Core 2.1.0.201306101322 org.eclipse.emf.compare.feature.group Eclipse Modeling Project
EMF Compare GMF Integration 2.1.0.201306101322 org.eclipse.emf.compare.diagram.gmf.feature.group Eclipse Modeling Project
EMF Compare IDE UI 2.1.0.201306101322 org.eclipse.emf.compare.ide.ui.feature.group Eclipse Modeling Project
EMF Compare Papyrus Integration 2.1.0.201306101322 org.eclipse.emf.compare.diagram.papyrus.feature.group Eclipse Modeling Project
EMF Compare UML2 Integration 2.1.0.201306101322 org.eclipse.emf.compare.uml2.feature.group Eclipse Modeling Project
EMF Diff/Merge SDK Feature (Incubation) 0.2.0.v20130523-0727 org.eclipse.emf.diffmerge.sdk.feature.feature.group Eclipse Modeling Project
EMF Facet SDK (Incubation) 0.3.0.v201212172149 org.eclipse.emf.facet.sdk.feature.feature.group Eclipse Modeling Project
EMF Model Query Examples 1.7.0.201306111332 org.eclipse.emf.query.examples.feature.group Eclipse Modeling Project
EMF Model Query SDK 1.7.0.201306111332 org.eclipse.emf.query.sdk.feature.group Eclipse Modeling Project
EMF Model Transaction Examples 1.7.0.201306111400 org.eclipse.emf.transaction.examples.feature.group Eclipse Modeling Project
EMF Model Transaction SDK 1.7.0.201306111400 org.eclipse.emf.transaction.sdk.feature.group Eclipse Modeling Project
EMF ODA Driver SDK 1.2.0.v20130610-0406 org.eclipse.emf.oda.sdk.feature.group Eclipse Modeling Project
EMF Teneo CDO SDK 2.0.1.v201301151903 org.eclipse.emf.teneo.cdo.sdk.feature.group Eclipse Modeling Project
EMF Teneo Hibernate Runtime 2.0.1.v201301151903 org.eclipse.emf.teneo.hibernate.feature.group Eclipse Modeling Project
EMF Teneo Hibernate SDK 2.0.1.v201301151903 org.eclipse.emf.teneo.hibernate.sdk.feature.group Eclipse Modeling Project
EMF Validation Framework Examples 1.7.0.201306111341 org.eclipse.emf.validation.examples.feature.group Eclipse Modeling Project
EMF Validation Framework SDK 1.7.0.201306111341 org.eclipse.emf.validation.sdk.feature.group Eclipse Modeling Project

OCL End User SDK 4.1.0.v20130611-1511 org.eclipse.ocl.all.sdk.feature.group Eclipse Modeling Project
OCL Examples and Editors 3.3.0.v20130611-1511 org.eclipse.ocl.examples.feature.group Eclipse Modeling Project
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynam [message #1075824 is a reply to message #1075820] Tue, 30 July 2013 02:21 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4003
Registered: July 2009
Senior Member
HI

I'm actually using EMF from GIT, but I see no changes to the codegen
templates since Kepler.

I don't have Xcore SDK installed, and since Xcore may well provide set
setting delegate support, that's where the problem may lie.

Regards

Ed Willink


On 30/07/2013 07:12, Kirsten M. Z. wrote:
> Ahhh... unfortunately not all version information is in the project.
>
> However, I use Kepler. I will copy some version Information. Can you
> see any important difference to your version?
>
> Version: Kepler Release
> Build id: 20130614-0229
>
> EMF - Eclipse Modeling Framework SDK 2.9.0.v20130610-0406
> org.eclipse.emf.sdk.feature.group Eclipse Modeling Project
> EMF - Eclipse Modeling Framework Xcore SDK 1.1.0.v20130612-0809
> org.eclipse.emf.ecore.xcore.sdk.feature.group Eclipse Modeling Project
> EMF Compare Core 2.1.0.201306101322
> org.eclipse.emf.compare.feature.group Eclipse Modeling Project
> EMF Compare GMF Integration 2.1.0.201306101322
> org.eclipse.emf.compare.diagram.gmf.feature.group Eclipse Modeling
> Project
> EMF Compare IDE UI 2.1.0.201306101322
> org.eclipse.emf.compare.ide.ui.feature.group Eclipse Modeling Project
> EMF Compare Papyrus Integration 2.1.0.201306101322
> org.eclipse.emf.compare.diagram.papyrus.feature.group Eclipse
> Modeling Project
> EMF Compare UML2 Integration 2.1.0.201306101322
> org.eclipse.emf.compare.uml2.feature.group Eclipse Modeling Project
> EMF Diff/Merge SDK Feature (Incubation) 0.2.0.v20130523-0727
> org.eclipse.emf.diffmerge.sdk.feature.feature.group Eclipse
> Modeling Project
> EMF Facet SDK (Incubation) 0.3.0.v201212172149
> org.eclipse.emf.facet.sdk.feature.feature.group Eclipse Modeling
> Project
> EMF Model Query Examples 1.7.0.201306111332
> org.eclipse.emf.query.examples.feature.group Eclipse Modeling Project
> EMF Model Query SDK 1.7.0.201306111332
> org.eclipse.emf.query.sdk.feature.group Eclipse Modeling Project
> EMF Model Transaction Examples 1.7.0.201306111400
> org.eclipse.emf.transaction.examples.feature.group Eclipse Modeling
> Project
> EMF Model Transaction SDK 1.7.0.201306111400
> org.eclipse.emf.transaction.sdk.feature.group Eclipse Modeling Project
> EMF ODA Driver SDK 1.2.0.v20130610-0406
> org.eclipse.emf.oda.sdk.feature.group Eclipse Modeling Project
> EMF Teneo CDO SDK 2.0.1.v201301151903
> org.eclipse.emf.teneo.cdo.sdk.feature.group Eclipse Modeling Project
> EMF Teneo Hibernate Runtime 2.0.1.v201301151903
> org.eclipse.emf.teneo.hibernate.feature.group Eclipse Modeling Project
> EMF Teneo Hibernate SDK 2.0.1.v201301151903
> org.eclipse.emf.teneo.hibernate.sdk.feature.group Eclipse Modeling
> Project
> EMF Validation Framework Examples 1.7.0.201306111341
> org.eclipse.emf.validation.examples.feature.group Eclipse Modeling
> Project
> EMF Validation Framework SDK 1.7.0.201306111341
> org.eclipse.emf.validation.sdk.feature.group Eclipse Modeling Project
>
> OCL End User SDK 4.1.0.v20130611-1511
> org.eclipse.ocl.all.sdk.feature.group Eclipse Modeling Project
> OCL Examples and Editors 3.3.0.v20130611-1511
> org.eclipse.ocl.examples.feature.group Eclipse Modeling Project
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSe [message #1075829 is a reply to message #1075810] Tue, 30 July 2013 02:40 Go to previous messageGo to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
Hmh, I downloaded standard Kepler, installed, created a new Workspace, regenerated the model etc.

I still get the following output:

0
100
Exception in thread "main" java.lang.UnsupportedOperationException
at org.eclipse.emf.ecore.util.BasicSettingDelegate$Stateless.set(BasicSettingDelegate.java:226)
at org.eclipse.emf.ecore.util.BasicSettingDelegate$Stateless.dynamicSet(BasicSettingDelegate.java:215)
at test.impl.MyClassImpl.setAttributeWithInitital(MyClassImpl.java:95)
at MyMain.main(MyMain.java:38)

version information:

Version: Kepler Release
Build id: 20130614-0229

Eclipse Standard/SDK 2.0.0.20130613-0530 epp.package.standard null
EMF - Eclipse Modeling Framework SDK 2.9.0.v20130610-0406 org.eclipse.emf.sdk.feature.group Eclipse Modeling Project
OCL Core SDK 4.1.0.v20130610-1317 org.eclipse.ocl.core.sdk.feature.group Eclipse Modeling Project
OCL End User SDK 4.1.0.v20130611-1511 org.eclipse.ocl.all.sdk.feature.group Eclipse Modeling Project
OCL Examples and Editors 3.3.0.v20130611-1511 org.eclipse.ocl.examples.feature.group Eclipse Modeling Project
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSe [message #1075843 is a reply to message #1075829] Tue, 30 July 2013 03:17 Go to previous messageGo to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
BTW:

Shouldn't the correct output be:

0
100
0
200

(your output was: 0,0,0,200)

Ok, I understand that setting delegates do not support "regular setting", but only for "derived". However, I work with "initial", which is a setting delegate according to http://wiki.eclipse.org/MDT/OCLinEcore (I don't understand why "setting delegate", but nvm). "Setting" an attribute initially is not really a model change (by OCL) I guess. I expect that a property with "initial" can be changed/set? Otherwise, I could use "derived"?!?
Re: [OCLinEcore] Setting Delegate (initial) => UnsupportedOperationException in dynamicSet [message #1077042 is a reply to message #1075407] Thu, 01 August 2013 03:07 Go to previous messageGo to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
Sorry to ask again, but right now I don't know how to continue modelling. Therefore, I will paste the code (from the eproject attached above) and ask if this is a bug:

String oclDelegateURI = OCLConstants.OCL_DELEGATE_URI;

org.eclipse.ocl.ecore.OCL.initialize(null);
EStructuralFeature.Internal.SettingDelegate.Factory.Registry.INSTANCE.put(oclDelegateURI, new OCLSettingDelegateFactory.Global());

MyClass m = TestFactory.eINSTANCE.createMyClass();
System.out.println(m.getAttributeWithoutInitital());
System.out.println(m.getAttributeWithInitital());
m.setAttributeWithInitital(200);
System.out.println(m.getAttributeWithoutInitital());
System.out.println(m.getAttributeWithInitital());


The model:

<?xml version="1.0" encoding="UTF-8"?>
<ecore:EPackage xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" name="test" nsURI="test" nsPrefix="test">
  <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore">
    <details key="invocationDelegates" value="http://www.eclipse.org/emf/2002/Ecore/OCL"/>
    <details key="settingDelegates" value="http://www.eclipse.org/emf/2002/Ecore/OCL"/>
    <details key="validationDelegates" value="http://www.eclipse.org/emf/2002/Ecore/OCL"/>
  </eAnnotations>
  <eClassifiers xsi:type="ecore:EClass" name="MyClass">
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="AttributeWithInitital"
        eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EInt">
      <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore/OCL">
        <details key="initial" value="100"/>
      </eAnnotations>
    </eStructuralFeatures>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="AttributeWithoutInitital"
        eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EInt"/>
  </eClassifiers>
</ecore:EPackage>


According to http://wiki.eclipse.org/MDT/OCLinEcore I expect the output:

0
100
0
200


However, I get

0
100
Exception in thread "main" java.lang.UnsupportedOperationException
 at org.eclipse.emf.ecore.util.BasicSettingDelegate$Stateless.set(BasicSettingDelegate.java:226)
 at org.eclipse.emf.ecore.util.BasicSettingDelegate$Stateless.dynamicSet(BasicSettingDelegate.java:215)
 at test.impl.MyClassImpl.setAttributeWithInitital(MyClassImpl.java:95)
 at MyMain.main(MyMain.java:38)


With another (current) version which ignores "initial" (see above), the output seems to be:

0
0
0
200


Is this a bug?
Re: [OCLinEcore] Setting Delegate (initial) =&gt; UnsupportedOperationException in dynamicSet [message #1077083 is a reply to message #1077042] Thu, 01 August 2013 04:16 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4003
Registered: July 2009
Senior Member
Hi

It's certainly puzzling.

I started to look at why GenModel is behaving differently in Juno and
Kepler but got distracted. I couln't see any relevany difference in
Class.javajet which would be the obvious location, so something more
subtle must have changed in EMF.

The concept of non-trivial initial expressions is a bit vague in EMF and
unsupported in UML. I recommend using derived expressions instead. NB
set the derived property true.

Regards

Ed Willink

On 01/08/2013 08:07, Kirsten M. Z. wrote:
> Sorry to ask again, but right now I don't know how to continue
> modelling. Therefore, I will paste the code (from the eproject
> attached above) and ask if this is a bug:
>
> String oclDelegateURI = OCLConstants.OCL_DELEGATE_URI;
>
> org.eclipse.ocl.ecore.OCL.initialize(null);
> EStructuralFeature.Internal.SettingDelegate.Factory.Registry.INSTANCE.put(oclDelegateURI,
> new OCLSettingDelegateFactory.Global());
>
> MyClass m = TestFactory.eINSTANCE.createMyClass();
> System.out.println(m.getAttributeWithoutInitital());
> System.out.println(m.getAttributeWithInitital());
> m.setAttributeWithInitital(200);
> System.out.println(m.getAttributeWithoutInitital());
> System.out.println(m.getAttributeWithInitital());
>
> The model:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ecore:EPackage xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" name="test"
> nsURI="test" nsPrefix="test">
> <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore">
> <details key="invocationDelegates"
> value="http://www.eclipse.org/emf/2002/Ecore/OCL"/>
> <details key="settingDelegates"
> value="http://www.eclipse.org/emf/2002/Ecore/OCL"/>
> <details key="validationDelegates"
> value="http://www.eclipse.org/emf/2002/Ecore/OCL"/>
> </eAnnotations>
> <eClassifiers xsi:type="ecore:EClass" name="MyClass">
> <eStructuralFeatures xsi:type="ecore:EAttribute"
> name="AttributeWithInitital"
> eType="ecore:EDataType
> http://www.eclipse.org/emf/2002/Ecore#//EInt">
> <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore/OCL">
> <details key="initial" value="100"/>
> </eAnnotations>
> </eStructuralFeatures>
> <eStructuralFeatures xsi:type="ecore:EAttribute"
> name="AttributeWithoutInitital"
> eType="ecore:EDataType
> http://www.eclipse.org/emf/2002/Ecore#//EInt"/>
> </eClassifiers>
> </ecore:EPackage>
>
> According to http://wiki.eclipse.org/MDT/OCLinEcore I expect the output:
>
> 0
> 100
> 0
> 200
>
> However, I get
>
> 0
> 100
> Exception in thread "main" java.lang.UnsupportedOperationException
> at
> org.eclipse.emf.ecore.util.BasicSettingDelegate$Stateless.set(BasicSettingDelegate.java:226)
> at
> org.eclipse.emf.ecore.util.BasicSettingDelegate$Stateless.dynamicSet(BasicSettingDelegate.java:215)
> at test.impl.MyClassImpl.setAttributeWithInitital(MyClassImpl.java:95)
> at MyMain.main(MyMain.java:38)
>
> With another (current) version which ignores "initial" (see above),
> the output seems to be:
>
> 0
> 0
> 0
> 200
>
> Is this a bug?
>
Re: [OCLinEcore] Setting Delegate (initial) =&gt; UnsupportedOperationException in dynamicSet [message #1077091 is a reply to message #1077083] Thu, 01 August 2013 04:34 Go to previous messageGo to next message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
> I recommend using derived expressions instead.

Ok, maybe I got something totally wrong, so please make a clear statement if I am wrong:

An attribute with initial value is not the same thing as a derived attribute.

If this is true, how can I use a derived expression instead? Using a derived expression/attribute in order to set an attribute initially? But how to set initially? And why is the current behavior of "initial" (OCLinEcore) not a bug then?

I am really puzzled Wink

[Updated on: Thu, 01 August 2013 04:36]

Report message to a moderator

Re: [OCLinEcore] Setting Delegate (initial) =&amp;gt; UnsupportedOperationException in dynamicSe [message #1077145 is a reply to message #1077091] Thu, 01 August 2013 05:45 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4003
Registered: July 2009
Senior Member
Hi

You don't have to use OCL for non-expressions; you can use the
traditional ECore defaultValueLiteral.

attribute AttributeWithInitital : ecore::EInt[?] = '100';

Regards

Ed Willink


On 01/08/2013 09:34, Kirsten M. Z. wrote:
>> I recommend using derived expressions instead.
>
> Ok, maybe I got something totally wrong, so please make a clear
> statement if I am wrong.
>
> an attribute with initial value is not the same thing as a derived
> attribute
>
> If this is true, how can I use a derived expression instead? Using an
> derived expression/attribute in order to set an attribute initially?
> But how to set initially? And why is the current behavior of "initial"
> (OCLinEcore) not a bug then?
>
> I am really puzzled ;)
>
Re: [OCLinEcore] Setting Delegate (initial) =&amp;gt; UnsupportedOperationException in dynamicSe [message #1077151 is a reply to message #1077145] Thu, 01 August 2013 05:56 Go to previous message
Kirsten M. Z. is currently offline Kirsten M. Z.
Messages: 131
Registered: July 2010
Senior Member
Yes, but the only intention of my example was to Show the bug (<- is it a bug?). I have more complex expressions, of course.

Therefore, I want to know what I have to expect from that OCLinEcore feature. Shall it work the way I expect? How is it expected to work?


[Updated on: Thu, 01 August 2013 05:56]

Report message to a moderator

Previous Topic:org.eclipse.ocl.examples.pivot.helper.OCLHelper syntax help
Next Topic:Structured Type Initialization
Goto Forum:
  


Current Time: Wed Jul 23 12:20:48 EDT 2014

Powered by FUDForum. Page generated in 0.02046 seconds