|
|
|
Re: Xtext validation using Complete OCL [message #1230301 is a reply to message #1230290] |
Sat, 11 January 2014 15:56 |
Ed Willink Messages: 7655 Registered: July 2009 |
Senior Member |
|
|
Hi
There has been steady evolution making OCL in Ecore steadily more
useable. As you note OCL inCDATA is not really tenable.
The OCL concrete syntax is very stable. It's the tooling that hopefully
gets better and better. So if you develop OCL futuire evolution should
only require peripheral tweaks.
I am a major supporter of OCL so I would certainly recommend it for
someone like you who won't get thrown by a minor hiccough.
Production-use? Well if you mention safety critical... Not today, but
there are few other approaches that can actually be better.
Realistically you have to see whether it's herlpful for you.
The classic Ecore-based OCL is very stable but has corner bugs that are
too hard to fix.
The new modelled pivot OCL used with Xtext is potentially much cleaner,
but if you look at some of the recent bug fixes, it's clearly not yet
perfect.
I would use OCLinEcore as first choice, or Complete OCL where you need
to separate structural and validation concerns.
[I'm still hoping to have a Validity View for detailed control of
constraints with the ability to fire off a debugger to investigate
failures for Luna.]
Regards
Ed Willink
On 11/01/2014 15:28, Vlad Gheorghe wrote:
> Hi Ed,
>
> Thanks for the reply.
>
> I found really useful to have the constraints in a separate file.
> I have used before EMFV constraints defined in xml files, but it was
> rather cumbersome.
>
> The current application uses xtext, so I gather EMFV is out of
> discussion.
> Our application must soon be in production - so I also have to
> consider the stability of the used components.
>
> What would you recommend to use for OCL validation of model instances
> of ecore-based metamodels, in production-use applications ?
>
> Best regards
> Vlad Gheorghe
>
>
>
>
>
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03206 seconds