I'm using CompleteOCL to attach OCL constraints to my UML model.
When using the CompleteOCL editor i get several errors when trying to use packages or classes (contexts)from my uml model. I import my metamodel to the ocl file as follows:
import '../../RangeDB_cdm.uml'
package MonitoringData::MonitoringGroups
context GRPK
--Value constraint String--
inv checkGRPKNameValue :
let name :String = self.GRPK_GNAME in
name.size()<=12
endpackage
The editor behaves really buggy. Did I do something wrong when importing my metamodel? Has anyone a good example how to use CompleteOCL in combination with UML?
Is there a problem with nested packages? Because the editor is not able to resolve classes in the package like in my example GRPK.
This is a very important request. And i am really looking forward to get some answers.
Is the question not clear. If this is the case please let me know so that i can clarify.
My newsgroup reader shows no previous message, so what is the question?
Regards
Ed Willink
On 27/07/2011 12:10, Ambros Morscher wrote:
> This is a very important request. And i am really looking forward to
> get some answers. Is the question not clear. If this is the case
> please let me know so that i can clarify.
Posted my problem/question again
I'm using CompleteOCL to attach OCL constraints to my UML model.
When using the CompleteOCL editor i get several errors when trying to use packages or classes (contexts)from my uml model. I import my metamodel to the ocl file as follows:
import '../../RangeDB_cdm.uml'
package MonitoringData::MonitoringGroups
context GRPK
--Value constraint String--
inv checkGRPKNameValue :
let name :String = self.GRPK_GNAME in
name.size()<=12
endpackage
The editor behaves really buggy. Did I do something wrong when importing my metamodel? Has anyone a good example how to use CompleteOCL in combination with UML?
Is there a problem with nested packages? Because the editor is not able to resolve classes in the package like in my example GRPK.
The addition of UML editing support was a late addition just in time for
Indigo. It uses a double translation from UML to Ecore and then to Pivot
even though a direct UML to Pivot should be much easier since the Pivot
is UML-derived. Unfortunately the profile support is not yet present so
via Ecore was a better option than no UML support.
I'm not entirely surprised that there are problems. Sorry. Can you raise
Bugzillas with example files so that I cannot forget about the problems.
Regards
Ed Willink
On 28/07/2011 12:12, Ambros Morscher wrote:
> Posted my problem/question again
> I'm using CompleteOCL to attach OCL constraints to my UML model.
> When using the CompleteOCL editor i get several errors when trying to
> use packages or classes (contexts)from my uml model. I import my
> metamodel to the ocl file as follows:
>
> import '../../RangeDB_cdm.uml'
>
>
> package MonitoringData::MonitoringGroups
>
> context GRPK
> --Value constraint String--
> inv checkGRPKNameValue :
> let name :String = self.GRPK_GNAME in
> name.size()<=12
> endpackage
>
> The editor behaves really buggy. Did I do something wrong when
> importing my metamodel? Has anyone a good example how to use
> CompleteOCL in combination with UML?
> Is there a problem with nested packages? Because the editor is not
> able to resolve classes in the package like in my example GRPK.
>